[ http://jira.codehaus.org/browse/MECLIPSE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90253 ]
Arnaud Heritier commented on MECLIPSE-107: ------------------------------------------ ok, thanks for your feedback. I'll add your test case in our tests and I'll fix it this WE. > Dependency Version Incorrectly Taken from DependencyManagement > -------------------------------------------------------------- > > Key: MECLIPSE-107 > URL: http://jira.codehaus.org/browse/MECLIPSE-107 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution > Affects Versions: 2.2 > Reporter: Stephen Duncan Jr > Priority: Critical > Attachments: dmtest.zip, > MECLIPSE-107-maven-eclipse-plugin-20061211-1200.patch > > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira