You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2008/10/03 17:46:08 UTC
[jira] Commented: (MASSEMBLY-314) Multiple inclusion of
dependencies in binary assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149816#action_149816 ]
Paul Gier commented on MASSEMBLY-314:
-------------------------------------
I just ran into this issue, and I can confirm that it can be fixed using the same {{archiverConfig}} configuration described in MASSEMBLY-285.
Can we change the default behavior of the assembly plugin? It seems like it makes more sense to not allow duplicates by default. Especially since, as Rainer described, the "dir" format will not include duplicates and you can end up with different contents for "dir" vs. "zip" for example.
> Multiple inclusion of dependencies in binary assembly
> -----------------------------------------------------
>
> Key: MASSEMBLY-314
> URL: http://jira.codehaus.org/browse/MASSEMBLY-314
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: all
> Reporter: Thorsten Möller
> Fix For: 2.2-beta-3
>
>
> Hello,
> today I tried to upgrade the Maven assembly plugin from 2.2-beta-1 to 2.2-beta-2. However, I noticed that for my project which consists of multiple modules the resulting binary assembly now contains dependency JAR files multiple times. The assembly descriptor contains the following excerpt (with changed module names):
> <moduleSets>
> <moduleSet>
> <includes>
> <include>${pom.groupId}:a</include>
> <include>${pom.groupId}:b</include>
> <include>${pom.groupId}:c</include>
> </includes>
> <binaries>
> <includeDependencies>true</includeDependencies>
> <unpack>false</unpack>
> <outputDirectory>/lib</outputDirectory>
> </binaries>
> </moduleSet>
> </moduleSets>
> The projects a, b, c have several dependencies, whereby some of those dependencies refer to identical artifacts (derived from a parent POM), e.g., commons-logging. The resulting ZIP and TAR.GZ assembly files then contain those dependencies multiple times (in the lib folder) with equal names! Im not sure if this is a bug or a feature and I might have missed something.
> I rolled back to version 2.2-beta-1 and I could reproduce the issue. 2.2-beta-1 works as expected, i.e., all files exist only once.
> Regards,
> Thorsten
--
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