[
http://jira.codehaus.org/browse/MASSEMBLY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-390:
--------------------------------------
Fix Version/s: (was: 2.2)
> No way to exclude moduleSet binary artifacts, while still including their
> dependencies
> --------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-390
> URL: http://jira.codehaus.org/browse/MASSEMBLY-390
> Project: Maven 2.x Assembly Plugin
> Issue Type: Wish
> Reporter: Ben Coughlan
> Assignee: John Casey
> Priority: Trivial
> Attachments: useModuleArtifact.patch
>
>
> There is no way to exclude a moduleSet binary artifact without excluding all
> of its dependencies. This is necessary when dependencies of different types
> need to be sorted into different deployment directories, to prevent the
> module artifacts being included everywhere.
> The patch attached provides an example implementation of what I am thinking.
> An example descriptor would be:
> {code}
> <assembly>
> ...
> <moduleSets>
> <!-- All Non Jar dependencies -->
> <moduleSet>
> ...
> <binaries>
> <useModuleArtifact>false</useModuleArtifact>
> <dependencySets>
> <dependencySet>
> <excludes>
> <exclude>*:jar</exclude>
> </excludes>
> </dependencySet>
> </dependencySets>
> <outputDirectory>nonjars</outputDirectory>
> </binaries>
> </moduleSet>
> <!-- All Jar dependencies -->
> <moduleSet>
> <binaries>
> <useModuleArtifact>false</useModuleArtifact>
> <dependencySets>
> <dependencySet>
> <includes>
> <include>*:jar</include>
> </includes>
> </dependencySet>
> </dependencySets>
> <outputDirectory>jars</outputDirectory>
> </binaries>
> </moduleSet>
> </moduleSets>
> </assembly>
> {code}
--
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
