[MASSEMBLY-393] Cannot Override dependencyManagement

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2-beta-3
• Fix Version/s: 2.2
• Environment: maven 2.0.9,2.0.10, windows xp, debian gnu linux, solaris 10
• Assignee: John Dennis Casey
• Reporter: deckrider
• Created: 25/Feb/09 07:46
• Updated: 28/Sep/10 15:28
• Resolved: 22/Sep/10 18:54

Description

This was not a problem in 2.2-beta-2.

I've provided a test case. It should produce a zip file containing log4j-1.2.14.jar but instead contains log4j-1.2.12.jar

To run the test case:

unzip my-app.zip
cd my-app.zip
mvn clean package

This is critical for us, because we have a master parent pom where we keep all our versions in a dependencyManagement section, but on occasion we want to override them. Upgrading from 2.2-beta-2 to 2.2-beta-3 broke that ability.

Issue Links

• is duplicated by: MASSEMBLY-247 versions of included dependencies in multi-module projects are not deterministic
• is duplicated by: MASSEMBLY-299 assembly does not honnor <dependencyManagement> directives
• is duplicated by: MASSEMBLY-432 assembly misapplies depMgt and selects the wrong dependency for an archive
• is related to: MASSEMBLY-235 dependencySet ignores dependency management