[MASSEMBLY-247] versions of included dependencies in multi-module projects are not deterministic

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 2.2-beta-2
• Environment: Maven 2.0.4 an assembly plugin 2.2-SNAPSHOT
• Assignee: John Dennis Casey
• Reporter: Tarek El-Sibay
• Created: 11/Oct/07 02:43
• Updated: 31/Jan/15 13:47
• Resolved: 23/Sep/10 09:30

Description

There is a problem with including dependency jars in an assembly. The resoultion of the version of the dependencies is not deterministic. The attached zipfile contains three projects, assembly, module-One and modue-Two. the assembly project is the aggregator of module-One and module-Two. module-One has a dep to junit 3.8.1, module-Two to junit 4.0. The assembly project contains a DependencyManagement with a dependency to junit 4.0. After executing 'mvn clean package ' in the assembly project the resulting zip file assembly-1.0-SNAPSHOT-luna.zip contains junit 3.8.1, after 'mvn clean install' it contains junit 4.0.
Sometimes its the other way around, but playing with both commands shows that the resulting version of junit is not deterministic.

Issue Links

• duplicates: MASSEMBLY-393 Cannot Override dependencyManagement
• is related to: MASSEMBLY-235 dependencySet ignores dependency management