[jira] Created: (MECLIPSE-107) Dependency Version Incorrectly Taken from DependencyManagement

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (MECLIPSE-107) Dependency Version Incorrectly Taken from DependencyManagement

JIRA jira@codehaus.org
Dependency Version Incorrectly Taken from DependencyManagement
--------------------------------------------------------------

         Key: MECLIPSE-107
         URL: http://jira.codehaus.org/browse/MECLIPSE-107
     Project: Maven 2.x Eclipse Plugin
        Type: Bug

    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

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (MECLIPSE-107) Dependency Version Incorrectly Taken from DependencyManagement

JIRA jira@codehaus.org
    [ http://jira.codehaus.org/browse/MECLIPSE-107?page=comments#action_66501 ]

Stephen Duncan Jr commented on MECLIPSE-107:
--------------------------------------------

I've verified that this also affects the Netbeans plugin.  And overriding the version (or scope) in dependencyManagement in the child pom fixes the problem.  Assumably, just a dependencyManagement section is required to reproduce this, even in a single project.  What shared component might be responsible?  Can/should this issue be moved, or should I try to create a new issue for Maven overall?

> Dependency Version Incorrectly Taken from DependencyManagement
> --------------------------------------------------------------
>
>          Key: MECLIPSE-107
>          URL: http://jira.codehaus.org/browse/MECLIPSE-107
>      Project: Maven 2.x Eclipse Plugin
>         Type: Bug

>     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