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.
When I change the version back to 2.2-beta-1 it works as expected, i.e., all
files exist only once.
Any hints?
Thanks,
Thorsten
--
View this message in context:
http://www.nabble.com/Assembly-plugin-2.2-beta-2-shows-odd-behavior-regarding-dependencies-inclusion-tp16720569s177p16720569.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
