You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Ryan Wynn (JIRA)" <ji...@apache.org> on 2007/05/11 01:26:43 UTC
[jira] Created: (SHALE-444) Eclipse Plugin
Eclipse Plugin
--------------
Key: SHALE-444
URL: https://issues.apache.org/struts/browse/SHALE-444
Project: Shale
Issue Type: New Feature
Components: Clay
Environment: Any environment supported by Eclipse
Reporter: Ryan Wynn
Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
Posted by "Hermod Opstvedt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40964 ]
Hermod Opstvedt commented on SHALE-444:
---------------------------------------
Wow - We have been waiting for this one for a long time - I'll be all over it in a couple of minutes.
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
Posted by "Gary VanMatre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41621 ]
Gary VanMatre commented on SHALE-444:
-------------------------------------
Committed the project to the sandbox for evaluation.
https://svn.apache.org/repos/asf/shale/sandbox/shale-eclipse-plugins
Coincidentally, I was lurking on the myfaces list and saw a post from a Dan Tran who turns out to be the author of the plugin.
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41094 ]
Brett Porter commented on SHALE-444:
------------------------------------
The software grant is certainly worth doing for good measure, though I'm not sure it is required if an iCLA is already on file for all past contributors. Reading the IP template seems to indicate one is needed, but AFAICT the terminology in the icla and the grant are the same (so the grant would just be for when the authors may or may not have a CLA on file, or just as an added measure of assurance to make the paper trail clearer).
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41117 ]
Henri Yandell commented on SHALE-444:
-------------------------------------
Sadly both of you are right. The Incubator stuff currently says a grant is needed, and the way of thinking seems to be that it shouldn't.
Am talking to legal about getting this sorted.
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
Posted by "Wendy Smoak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40969 ]
Wendy Smoak commented on SHALE-444:
-----------------------------------
Thanks, Ryan!
Because this is "a substantial contribution that was not developed within the ASF's source control system and on our public mailing lists," it will need to go through the Incubator IP clearance process, as described here: http://incubator.apache.org/ip-clearance/index.html
A quick read through indicates that we need two more things from Ryan...
1) a checksum (md5 hash) for the zip file
2) a software grant - http://www.apache.org/licenses/software-grant.txt
There were license headers on the few files I looked at, and Ryan already has an iCLA on file.
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
Posted by "Ryan Wynn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41161 ]
Ryan Wynn commented on SHALE-444:
---------------------------------
md5sum - b038c63fced4b25024c5d41f995296e9
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
Posted by "Gary VanMatre (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41563 ]
Gary VanMatre commented on SHALE-444:
-------------------------------------
I still have not be successful in creating a Maven build for this eclipse plugin. I've been trying to use an alpha maven pde plugin [1]. This plugin creates an ant build script and then launches eclipse in headless mode. The eclipse IDE is still required. I've tried contacting the primary author but the mail account is not active.
Another interesting twist is that Ryan's eclipse plugin has several dependencies to libraries that can be found in maven repositories. It would be nice if we could get maven to pull these down into a lib folder under the plugin project. I was thinking that we could create our own mojo to pull the projects compile dependencies and drop them in the lib folder.
The maven pde plugin is under an apache license so we could pull it in as a base to start from. However, would it be worth the effort considering the IDE is required to create a deployable plugin artifact?
At the very minimum, a mojo to fixup the project dependencies would be helpful. Deploying for eclipse is only a couple clicks.
I feel we need to get this code in our repository but wanted to have a good build. Any objections to committing to the sandbox so you maven mavens can take a look?
[1] http://mojo.codehaus.org/pde-maven-plugin/
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
Posted by "Hermod Opstvedt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41132 ]
Hermod Opstvedt commented on SHALE-444:
---------------------------------------
Here are som bug fixes:
AttributesMetadataCellModifier.java
Lines 75-83:
case 2:
stringValue = attribute.getBindingType();
choices = metadataComponent.getChoices(property);
i = choices.length - 1;
+ //StringValue can be null
- while (!stringValue.equals(choices[i]) && i > 0)
+ while (stringValue!=null && !stringValue.equals(choices[i]) && i > 0)
--i;
result = new Integer(i);
break;
AttributesMetadataComponent.java
Lines 405-413
+ // Current can be null
- while (current.getExtends() != null) {
+ while (current!=null && current.getExtends() != null) {
current = (ComponentBean) model.getConfig(project).getDisplayElements().get(current.getExtends());
+ // Current can be null
- if (current.getAttributes() != null) {
+ if (current != null && current.getAttributes() != null) {
attributes.addAll(current.getAttributes().keySet());
}
}
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-444) Eclipse Plugin
Posted by "Ryan Wynn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Wynn updated SHALE-444:
----------------------------
Attachment: shale-clay-plugin-src.zip
This is a zipped up Eclipse Plugin project containing the src code for a basic Shale clay plugin. This plugin has runtime dependencies which must be added to the project before it will run. These dependencies are not packaged with the attached source.
The runtime dependencies are commons-beanutils, commons-collections, commons-logging, commons-digester, shale-clay, shale-core, and servlet-api.jar It is expected that these libraries with be provided in the /lib directory under the root of the project.
Also, you will need to make sure you have the gef and xerces plugins installed in eclipse.
> Eclipse Plugin
> --------------
>
> Key: SHALE-444
> URL: https://issues.apache.org/struts/browse/SHALE-444
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Environment: Any environment supported by Eclipse
> Reporter: Ryan Wynn
> Attachments: shale-clay-plugin-src.zip
>
>
> Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.