[
https://jira.codehaus.org/browse/MASSEMBLY-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Seieroe updated MASSEMBLY-619:
------------------------------------
Attachment: pom.xml
assembly.xml
Here is a small sample pom and assembly descriptor to test with. The directory
"dir2" should be filled with the activemq-osgi artifact only since I'm
excluding the other dependency, commons-configuration. If you use the
maven-assembly-plugin version 2.2-beta-5 then dir2 only contains one jar file,
like I expect. If you run with a newer version, it contains 104 jar files.
> Configurations of different <dependencySet>s influence each other
> -----------------------------------------------------------------
>
> Key: MASSEMBLY-619
> URL: https://jira.codehaus.org/browse/MASSEMBLY-619
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: dependencySet
> Affects Versions: 2.2.2, 2.3
> Environment: Mqven 3.0.4, JDK 1.7
> Reporter: Olaf Otto
> Priority: Minor
> Attachments: assembly.xml, pom.xml
>
>
> When configuring two <dependencySet> elements, the configurations in the
> second influence the first one.
> h2. Reproduction:
> The following configuration utilizes to sets to copy different elements of
> the dependency hierarchy of a module into two distinct subfolders:
> {code:xml}
> <dependencySet>
> <outputDirectory>software</outputDirectory>
> <useProjectArtifact>false</useProjectArtifact>
> <excludes>
> <exclude>org.codehaus.groovy:*</exclude>
> </excludes>
> <useTransitiveDependencies>false</useTransitiveDependencies>
> </dependencySet>
> <dependencySet>
> <outputDirectory>libs</outputDirectory>
> <useProjectArtifact>false</useProjectArtifact>
> <includes>
> <include>org.codehaus.groovy:groovy-all</include>
> </includes>
> </dependencySet>
> {code}
> However, the first <dependencySet> unexpectedly contains most of the
> transitive dependencies. The issue can only be resolved by adding
> <useTransitiveDependencies>false</useTransitiveDependencies> to the second
> <dependencySet>, too. The issue remains reproducible when changing <scope>
> <outputMapping> etc. I suppose the isolation of the set configuration is
> broken. I could reproduce the issue with both 2.3 and 2.2.2.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
