maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damien Lecan (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-107) Dependency Version Incorrectly Taken from DependencyManagement
Date Mon, 20 Nov 2006 17:17:32 GMT
    [ http://jira.codehaus.org/browse/MECLIPSE-107?page=comments#action_80581 ] 
            
Damien Lecan commented on MECLIPSE-107:
---------------------------------------

I have the same problem, which is very annoying for me.

Someone could work on that ?

> 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

        

Mime
View raw message