[
http://jira.codehaus.org/browse/MECLIPSE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90243
]
Damien Lecan commented on MECLIPSE-107:
---------------------------------------
I checked out last source code of maven-eclipse-plugin, svn revision 494359
Fix doesn't work :
- neither on my real projects,
- nor on dmtest.zip provided test case
- nor on MECLIPSE-107-maven-eclipse-plugin-20061211-1200.patch provided test
case too.
Debug logs on dmtest.zip provided with this bug :
{noformat}...
[INFO] Reactor build order:
[INFO] Unnamed - com.stephenduncanjr:dmtest:pom:1.0-SNAPSHOT
[INFO] Unnamed - com.stephenduncanjr:dmtest-child:jar:1.0-SNAPSHOT
...
[DEBUG]
org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.4-SNAPSHOT:runtime
(selected for runtime)
...
[INFO] [eclipse:eclipse]
[DEBUG] com.stephenduncanjr:dmtest-child:jar:1.0-SNAPSHOT (selected for null)
[DEBUG] log4j:log4j:jar:1.2.13:compile (applying version: 1.2.8;)
[DEBUG] log4j:log4j:jar:1.2.8:compile (selected for compile)
...
{noformat}
In com.stephenduncanjr:dmtest-child, log4j:log4j:jar:1.2.13 should have been
used, but the plugin still wants to select version 1.2.8.
In the .classpath file of child module, I get that :
{noformat}
<classpathentry kind="var" path="M2_REPO/log4j/log4j/1.2.8/log4j-1.2.8.jar"/>
{noformat}
> 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
