[
http://jira.codehaus.org/browse/MASSEMBLY-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-202:
---------------------------------
Fix Version/s: 2.2
> Silent failure: <outputFileNameMapping> declared with multiple includes
> -----------------------------------------------------------------------
>
> Key: MASSEMBLY-202
> URL: http://jira.codehaus.org/browse/MASSEMBLY-202
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Environment: java version "1.5.0_09"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b01, mixed mode)
> Reporter: Graham Leggett
> Fix For: 2.2
>
>
> When attempting to add a dependency to an assembly _without_ unpacking the
> dependency using the following snippet of assembly, the dependecies are
> silently ignored:
> <dependencySet>
> <outputDirectory></outputDirectory>
> <outputFileNameMapping></outputFileNameMapping>
> <includes>
> <include>alchemy:alchemy-quant:jar:${os-platform}</include>
> <include>alchemy:alchemy-quant:ctf:${os-platform}</include>
> </includes>
> <unpack>false</unpack>
> <scope>runtime</scope>
> </dependencySet>
> It turns out the above config makes no sense - multiple dependencies match
> the includes rule, and yet an outputFileNameMapping has been defined, which
> only makes sense when it matches a single include line.
> In this case a proper error message needs to be thrown to explain that when
> outputFileNameMapping is present, only one include can be present. Currently
> assembly succeeds silently while doing nothing, causing much confusion.
--
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
