[MECLIPSE-107] Dependency Version Incorrectly Taken from DependencyManagement

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.5
• Component/s: Core : Dependencies resolution and build path (.classpath)
• Assignee: Arnaud Heritier
• Reporter: Stephen Charles Duncan, Jr.
• Created: 15/May/06 20:55
• Updated: 29/Nov/07 19:42
• Resolved: 29/Nov/07 19:42

Description

The version used when generating .classpath is taken from dependencyManagement even though the child pom sets the dependency version, which should override what is in dependencyManagement. This is a regression from the correct behaviour in 2.1.

The attached project demonstrates the problem. The .classpath file generated for the "child" project should specify log4j-1.2.13, but instead specifies 1.28.

Issue Links

• duplicates: MNG-2340 Incorrect dependency version downloaded