You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Allan Ramirez (JIRA)" <ji...@codehaus.org> on 2006/03/13 12:24:31 UTC
[jira] Closed: (MASSEMBLY-68) Need method to exclude all child
dependencies when creating a jar
[ http://jira.codehaus.org/browse/MASSEMBLY-68?page=all ]
Allan Ramirez closed MASSEMBLY-68:
----------------------------------
Resolution: Fixed
-added new parameter called projectModulesOnly where it assembles all the project modules without their dependencies.
To use command
mvn assembly:assembly -DprojectModulesOnly=true
> Need method to exclude all child dependencies when creating a jar
> -----------------------------------------------------------------
>
> Key: MASSEMBLY-68
> URL: http://jira.codehaus.org/browse/MASSEMBLY-68
> Project: Maven 2.x Assembly Plugin
> Type: Improvement
> Reporter: Dan Diephouse
> Assignee: Allan Ramirez
> Fix For: 2.1
>
> Original Estimate: 12 hours
> Remaining: 12 hours
>
> With xfire, we have 10 different modules. We want to create an "xfire-all" jar that has all the xfire modules bundled. We can do this with the assembly plugin right now by creating a pom with all our modules in it. However, when it includes all the child dependencies. To exclude child dependencies you have to listen them individually. XFire probably has around 50+ dependencies spread out over the build. Maintaining this exclude list would be too much work, so we'd like a way to simply say - build a jar composed of these 10 jars, but none of their deps.
--
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