[MNG-4768] Depending on declaration order, nearest matching version does not win when version range is involved in conflict - ASF JIRA

XML

Word

Printable

JSON

Consider these two dirty trees that differ only by the order of direct dependencies:

project
+- a:1.0
+- b:0.1
|  \- c:0.1
|     \- a:[2.0,3)
\- d:0.1
   \- a:2.0

project
+- a:1.0
+- d:0.1
|  \- a:2.0
\- b:0.1
   \- c:0.1
      \- a:[2.0,3)

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

is related to

MNG-820 Over-zealous transitive dependencies during mediation

MNG-303 dependency mediation and conflict management

relates to

MNG-4690 Transitive dependency lost when included another dependency