[
http://jira.codehaus.org/browse/MASSEMBLY-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrice BELLINGARD updated MASSEMBLY-226:
-----------------------------------------
Fix Version/s: 2.2-beta-2
> Filters as read-only parameter can break the assembly build of a multi-module
> project
> -------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-226
> URL: http://jira.codehaus.org/browse/MASSEMBLY-226
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Reporter: Fabrice BELLINGARD
> Assignee: Fabrice BELLINGARD
> Fix For: 2.2-beta-2
>
> Attachments: FiltersNotReadOnly.patch, FiltersTest.zip
>
>
> When I specify <build><filters> in the root project for filtering files of an
> assembly, then running "assembly:assembly" breaks. This is because
> <build><filters> configuration is inherited in the modules, and Maven does
> not correctly inherit this configuration (see MNG-2445).
> I attached an example project to test this:
> - run "assembly:attached" on the root project: it works fine
> - run "assembly:assembly" on the root project: it breaks
> I think the "filters" argument of the assembly plugin should not be
> read-only. Instead, it should be possible to redefine it locally, or leave it
> blank if we want the plugin to take the <build><filters> definition instead.
> What do you think of this? I can work on this.
--
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
