You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nicolas Peeters (JIRA)" <ji...@codehaus.org> on 2006/08/02 08:22:31 UTC
[jira] Commented: (MNGECLIPSE-77) Add support for WSAD specifics on
a J2EE project.
[ http://jira.codehaus.org/browse/MNGECLIPSE-77?page=comments#action_71343 ]
Nicolas Peeters commented on MNGECLIPSE-77:
-------------------------------------------
Are you guys aware of that? http://jira.codehaus.org/browse/MECLIPSE-137
It looks pretty promising!
> Add support for WSAD specifics on a J2EE project.
> -------------------------------------------------
>
> Key: MNGECLIPSE-77
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-77
> Project: Maven 2.x Extension for Eclipse
> Issue Type: New Feature
> Reporter: Joakim Erdfelt
> Priority: Minor
> Attachments: sample-projects-wsad6.x.tar.bz2
>
>
> Need the ability to support the WSAD / J2EE specific configurations.
> The Eclipse extension needs to either ...
> # map the WSAD / J2EE project directory structure to a Maven pom.
> This way allows the user to use the WSAD J2EE wizards.
> # map a Maven J2EE pom to the WSAD / J2EE project configuration.
> This way makes Maven the start of all J2EE applications.
> This could be done by Eclipse extension specifics, or
> with the use of pre-defined Archetypes that show up on the New Project / Maven Archetype Wizards within Eclipse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira