[
http://jira.codehaus.org/browse/MASSEMBLY-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121785
]
Paul Gier commented on MASSEMBLY-278:
-------------------------------------
A quick question about your use case. Do you configure the parent pom with a
list of several assembly descriptors and then want the child projects to just
use the descriptors that they find from the list?
Another option would be to configure the descriptorSourceDirectory in the
parent, and then each child will use the descriptors in it's own src path.
> Do not fail on missing descriptors
> ----------------------------------
>
> Key: MASSEMBLY-278
> URL: http://jira.codehaus.org/browse/MASSEMBLY-278
> Project: Maven 2.x Assembly Plugin
> Issue Type: Improvement
> Affects Versions: 2.2-beta-1
> Reporter: Sejal Patel
>
> Assembly requires too much boilerplate right now to be used in a reactor
> based project because of the way it fails out if no descriptors are found. I
> suggest adding a boolean parameter (probably ignoreMissingDescriptors) which
> can default to false for backwards compatability but when set to true, does
> nothing if no descriptors are found.
> Then in org.apache.maven.plugin.assembly.io.DefaultAssemblyReader line 131
> add the check for that new parameter so that it only fails out if it was
> configured to fail out. Otherwise it just goes about its business of assembly
> nothing (which seems like a perfectly reasonable logic as well).
> By doing these things, it makes it possible to configure the assembly plugin
> 1 time in a parent pom and then not have to configure it in several (in my
> case 11 out of 19) different modules again and again.
--
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
