[MASSEMBLY-619] Configurations of different <dependencySet>s influence each other

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.2.2, 2.3
• Fix Version/s: 2.5.1
• Component/s: dependencySet
• Environment: Mqven 3.0.4, JDK 1.7
• Assignee: Kristian Rosenvold
• Reporter: Olaf Otto
• Created: 17/Jul/12 08:31
• Updated: 03/Nov/14 12:28
• Resolved: 03/Nov/14 12:28

Description

When configuring two <dependencySet> elements, the configurations in the second influence the first one.

Reproduction:

The following configuration utilizes to sets to copy different elements of the dependency hierarchy of a module into two distinct subfolders:

<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>

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.