You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2012/10/27 00:02:13 UTC
[jira] (MASSEMBLY-571) moduleSet dependencies processed incorrectly
[ https://jira.codehaus.org/browse/MASSEMBLY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MASSEMBLY-571:
--------------------------------------
Description:
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)
was:
Following configuration:
<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>
Results in bunch of:
[INFO] lib/my-app-0.0.1.${extension} already added, skipping
with assembly plugin in version 2.2.1
NOTE: but it works correctly (and as expected with version: 2.2-beta-1)
Summary: moduleSet dependencies processed incorrectly (was: moduleSet dependencies processed incorrecrly)
> moduleSet dependencies processed incorrectly
> --------------------------------------------
>
> Key: MASSEMBLY-571
> URL: https://jira.codehaus.org/browse/MASSEMBLY-571
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira