maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Perepelytsya (JIRA)" <>
Subject [jira] Commented: (MNGECLIPSE-77) Add support for WSAD specifics on a J2EE project.
Date Thu, 31 Aug 2006 03:21:05 GMT
    [ ] 
Andrew Perepelytsya commented on MNGECLIPSE-77:


I don't understand your comment. We *are* talking about maven-eclipse plugin and nothing else
here. Both WSAD and RAD6 plugin extensions reuse much of the original maven-eclipse plugin,
so it's only natural to bring it all under one umbrella and refactor/reuse the code. It's
trivial to bind those extensions to their own goals, e.g. _mvn eclipse:wsad_ would be a major
entry point for WSAD (in fact it is what I did and works well).

> Add support for WSAD specifics on a J2EE project.
> -------------------------------------------------
>                 Key: MNGECLIPSE-77
>                 URL:
>             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:
For more information on JIRA, see:


View raw message