[ http://jira.codehaus.org/browse/MNG-1452?page=all ]
John Casey updated MNG-1452:
----------------------------
Fix Version: 2.0.5
> best practices: deployment of aggregate JARs produced by the assembly plug-in
> -----------------------------------------------------------------------------
>
> Key: MNG-1452
> URL: http://jira.codehaus.org/browse/MNG-1452
> Project: Maven 2
> Type: Task
> Components: Design, Patterns & Best Practices
> Reporter: Jason van Zyl
> Priority: Trivial
> Fix For: 2.0.5
>
>
> We need a way to deploy aggregate JARs produced by the assembly plug-in. Some
> things to consider:
> 1) A new POM will need to be created to reflect the contents of the aggregate
> JAR
> 2) Do we want a standard name or classifier for these aggregate JARs, one
> standard name might not be enough as different assemblies for the same
> project might contain slightly different things.
> 3) Do we want assemblies like this to be in their own builds? Right now the
> J2EE JAR in the Geronimo build is like this whereas the assembly for the
> embedder is part of the embedder build. Would separating the build make it
> easier to deploy? Maybe.
--
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
