[jira] Updated: (MNG-3800) dependencyManagement ignores version constraints

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3800:
------------------------------

    Fix Version/s: 2.0.x

> dependencyManagement ignores version constraints
> ------------------------------------------------
>
>                 Key: MNG-3800
>                 URL: http://jira.codehaus.org/browse/MNG-3800
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.0.9
>            Reporter: Kees van Dieren
>             Fix For: 2.0.x
>
>
> Tested the following situation:
> ProjectA (version 0.5.0)
> ProjectB version 0.4.0 has dependency on projectA, with range [0.5.0,)
> ProjectC has a dependencyManagement section, in which projectA is defined on version 0.4.0 and projectB is defined on version 0.4.0
> Maven should warn us that this will not work: projectB requires version 0.5.0 or higher, however this doesn't say anything about this, and just works.
> We have tried the following versions in dependencyManagement:
> <version>[0.4.0]</version>
> <version>0.4.0</version>
> From ranges perspective, I would expect that [0.4.0] should be the correct one. However, than the dependencyManagent version gets ignored!
> Version 0.4.0 makes the dependencyManagement apply, but the build does not fail on range constraints.
> According to MNG-3396 it should have been solved in 2.0.9, quote from issue: " If you try to force a version out of the range in the dependencyManagement it is ignored."
> However, we are using that and we still have this problem.

-- 
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