[ 
http://jira.codehaus.org/browse/MASSEMBLY-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121797
 ] 

Sejal Patel commented on MASSEMBLY-278:
---------------------------------------

Yes I just want to configure it 1 time in the parent pom and then all the child 
projects just automatically invoke 1 of the descriptors (like descriptor.xml).

However, the descriptorSourceDirectory does not work because the first time it 
finds a child that does NOT have a descriptor folder, it fails out. Thus the 
reason I was hoping to have this flag to tell it not to error out just because 
there is no descriptors for it to use.

> 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

        

Reply via email to