[jira] Updated: (MNG-4768) Depending on declaration order, nearest matching version does not win when version range is involved in conflict

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

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

Benjamin Bentmann updated MNG-4768:
-----------------------------------

          Component/s:     (was: Integration Tests)
                       Dependencies
          Description: 
Consider these two dirty trees that differ only by the order of direct dependencies:
{noformat}
project
+- a:1.0
+- b:0.1
|  \- c:0.1
|     \- a:[2.0,3)
\- d:0.1
   \- a:2.0
{noformat}
{noformat}
project
+- a:1.0
+- d:0.1
|  \- a:2.0
\- b:0.1
   \- c:0.1
      \- a:[2.0,3)
{noformat}
Further assume the repository contains version 1.0, 2.0 and 2.1 of {{a}}. Also note that each occurrence of {{a}} appears on a different tree depth.

The first tree picks version 2.0, the latter 2.1 (from the range), although 2.0 is the nearer declaration (lower depth).

  was:
Verify that for a dirty tree like
{noformat}
project
+- a:1.0
+- b:0.1
|  \- c:0.1
|     \- a:[2.0,3)
\- d:0.1
   \- a:2.0
{noformat}
the selected version of {{a}} is 2.0, i.e. the nearest version that matches all hard constraints imposed by ranges.

             Priority: Major  (was: Minor)
    Affects Version/s: 2.2.1
                       3.0-beta-2
           Issue Type: Bug  (was: Task)
              Summary: Depending on declaration order, nearest matching version does not win when version range is involved in conflict  (was: Create integration test to check nearest-match wins when using version ranges)

> Depending on declaration order, nearest matching version does not win when version range is involved in conflict
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4768
>                 URL: http://jira.codehaus.org/browse/MNG-4768
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 2.2.1, 3.0-beta-2
>            Reporter: Benjamin Bentmann
>
> Consider these two dirty trees that differ only by the order of direct dependencies:
> {noformat}
> project
> +- a:1.0
> +- b:0.1
> |  \- c:0.1
> |     \- a:[2.0,3)
> \- d:0.1
>    \- a:2.0
> {noformat}
> {noformat}
> project
> +- a:1.0
> +- d:0.1
> |  \- a:2.0
> \- b:0.1
>    \- c:0.1
>       \- a:[2.0,3)
> {noformat}
> Further assume the repository contains version 1.0, 2.0 and 2.1 of {{a}}. Also note that each occurrence of {{a}} appears on a different tree depth.
> The first tree picks version 2.0, the latter 2.1 (from the range), although 2.0 is the nearer declaration (lower depth).

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