[
http://jira.codehaus.org/browse/MASSEMBLY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148999#action_148999
]
John Casey commented on MASSEMBLY-314:
--------------------------------------
If you're talking about adding the exact same dependency artifacts to the exact
same *path within the archive* several times, then it would be a great help to
get a test project that expresses this problem. If you could attach one, that
would help to illuminate this problem...if this is the case, I suspect it's
related to another issue we solved for 2.2-beta-3: MASSEMBLY-285.
Otherwise, it's perfectly reasonable to assume that when constructing an
assembly, modules should have all included dependencies added to their
respective locations within the archive, without editing them for duplicates
automatically. If you're constructing something like an EAR using the assembly
plugin, perhaps you should create a common location for these dependencies, and
exclude them from the other modules' dependencySets? Surely you can see that
editing for duplicates automatically will affect other legitimate use cases,
where users will have no control at all over what module dependencies land
where...
> 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
