[ http://jira.codehaus.org/browse/MECLIPSE-107?page=comments#action_81468 ] Andreas Guther commented on MECLIPSE-107: -----------------------------------------
Managed dependencies need to be taken into account, but they need to be overwritten by the component pom in those cases where the component pom needs to specify the version against the definition in the parent pom. This is the behavior in Maven and must be the same in the Eclipse plugin. I have the scenario where we manage our version in a parent pom with the dependencyManagement section. Usually our components do not specify the version which then is taken as specified in the parent pom. Just today I had the situation where I needed to overwrite the version in only one component for test reasons. Getting the fix is highly appreciated. > 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 > > > 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
