[ http://jira.codehaus.org/browse/MNG-576?page=all ]
John Casey updated MNG-576:
---------------------------
Priority: Blocker (was: Minor)
Escalating the priority on this, since patching maven-core isn't appropriate
for new packaging handlers. The object of the game is to allow new
type/package handlers to be added on the fly without modifying maven-core.
However, unless I'm mistaken, these new lifecycle mappings will not be
available simply by adding the type-handler plugin to the mix.
This will require some design time, so I'm going to make it a high priority.
> Support of EAR lifecycle
> ------------------------
>
> Key: MNG-576
> URL: http://jira.codehaus.org/browse/MNG-576
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins, maven-core
> Versions: 2.0-alpha-3
> Reporter: Stephane Nicoll
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
> Attachments: maven-core-ear-lifecycle.patch, maven-ear-lifecycle.patch
>
>
> The following patches integrates the ear plugin into a m2 lifecycle so that
> m2 package / install / deploy / etc goals could be used with an 'ear'
> packaging.
> First patch is to be applied on maven-core to register ear lifecycle
> Second patch is to be applied on maven-plugins/maven-ear-plugin to add
> support of generateApplicationXml flag which states whether application.xml
> should be generated or not (default is true).
> This relates to MNG-563 where the original discussion took place.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
