[MASSEMBLY-432] assembly misapplies depMgt and selects the wrong dependency for an archive

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2-beta-3
• Fix Version/s: 2.2
• Assignee: John Dennis Casey
• Reporter: Brian E Fox
• Created: 10/Jul/09 20:24
• Updated: 10/Mar/16 13:53
• Resolved: 21/Sep/10 16:09

Description

Here's the setup:

Parent has a depMgt set to version 1.3.4
Child has a dependency on 1.3.5

Assembly descriptor includes this dependency and 1.3.4 is bundled in, not 1.3.5.

See attached project for a working example. First install the parent, second run package on the child. See the zip contains 1.3.4 instead of 1.3.5.

Note: The real project where this happened has a property in the depMgt, if you use 2.0.10 this bug seems to not occur because the version is not interpolated in the pom that gets deployed. In 2.2 it is and causes this to manifest in the way I set it up, but fixing the version in the depMgt instead of using the property.

Issue Links

• duplicates: MASSEMBLY-393 Cannot Override dependencyManagement