[
https://jira.codehaus.org/browse/MASSEMBLY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355522#comment-355522
]
Kristian Rosenvold edited comment on MASSEMBLY-571 at 11/4/14 2:27 AM:
-----------------------------------------------------------------------
The outputFileMapping you have specified is expected to write to the artifact
output, so the behaviour is correct. Due the fix for MASSEMBLY-727 the
recommended solution for this is probably to just remove the
outputFileNameMapping element altogether since the new default value is
probably sufficient for most users
was (Author: krosenvold):
The outputFileMapping you have specified is expected to write to the artifact
output, so the behaviour is incorrect. Due the fix for MASSEMBLY-727 the
recommended solution for this is probably to just remove the
outputFileNameMapping element altogether since the new default value is
probably sufficient for most users
> moduleSet dependencies processed incorrectly
> --------------------------------------------
>
> Key: MASSEMBLY-571
> URL: https://jira.codehaus.org/browse/MASSEMBLY-571
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: moduleSet
> Affects Versions: 2.2.1
> Environment: any
> Reporter: Paul Green
> Assignee: Kristian Rosenvold
> Priority: Critical
> Fix For: 2.5.1
>
>
> Following configuration:
> {code:xml}
> <moduleSet>
> <includes>
> <include>com.example:extra-hiper-app</include>
> </includes>
> <binaries>
>
> <outputFileNameMapping>my-app.${extension}</outputFileNameMapping>
> <outputDirectory>output/lib</outputDirectory>
> <unpack>false</unpack>
> <includeDependencies>true</includeDependencies>
> <dependencySets>
> <dependencySet>
>
> <outputFileNameMapping>${artifactId}-${version}.${extension}</outputFileNameMapping>
> </dependencySet>
> </dependencySets>
> </binaries>
> </moduleSet>
> {code}
> Results in bunch of:
> {noformat}
> [INFO] lib/my-app-0.0.1.${extension} already added, skipping
> {noformat}
> with assembly plugin in version 2.2.1
> NOTE: but it works correctly (and as expected with version: 2.2-beta-1)
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
