[
https://jira.codehaus.org/browse/MASSEMBLY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355516#comment-355516
]
Kristian Rosenvold commented on MASSEMBLY-571:
----------------------------------------------
This is the interpolation expression artifactId evaluating towards the main
project artifact, causing this to be overwritten by every dependency jar file.
You must use something like ${artifact.artifactId} and ${artifact.extension}
to get the correct output filename. I'm trying to find out if there's something
we can do about this, but changing the values should fix the problem
> 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
> Priority: Critical
>
> 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)
