Mailing-List: contact issues-help@shale.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shale.apache.org
Message-ID: <13167667.1185156725061.JavaMail.jira@brutus>
Date: Sun, 22 Jul 2007 19:12:05 -0700 (PDT)
From: "Gary VanMatre (JIRA)" <jira@apache.org>
To: issues@shale.apache.org
Subject: [jira] Commented: (SHALE-444) Eclipse Plugin
In-Reply-To: <14830203.1178839603063.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ 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.