[ http://jira.codehaus.org/browse/MECLIPSE-107?page=all ]
Damien Lecan updated MECLIPSE-107:
----------------------------------
Attachment: MECLIPSE-107-maven-eclipse-plugin-20061211-1200.patch
Here is a patch to provide new test case to test this problem in the special
plugin test environment
I added a new module-3 into the list of master-test submodules which is itself
the parent of 2 new modules (submodule-1 and submodule-2)
module-3 describes a new managed dependecy (junit 2.0) which is used as-is be
submodule-1 and overriden by submodule-2 (which needs version junit 3.0)
I added new helpers methods in AbstractEclipsePluginTestCase class to handle
artifact version comparisons
Only "compile" scope is tested. Others scopes might be considered later (new
bug to fill in ?)
> 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
