Hi Jörg, As far as I know, Maven has no notion of "major" vs. "minor" vs. "patch" versions in the style of e.g. SemVer.
It simply judges which version is the newest via its algorithm, and uses the newest, since it is assumed that a dependency on e.g. 3.2.0 means "version must be at least as new as 3.2.0". Regards, Curtis -- Curtis Rueden LOCI software architect - https://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden On Fri, Apr 21, 2017 at 6:18 PM, Jörg Wille <joerg.wi...@gmail.com> wrote: > In a project 2 "different" versions of the same library A are used. One, as > a direct dependency with a snapshot version *3.2.1-SNAPSHOT* and the same > library - but with version *3.2.0* - is being used as a transient > dependency in yet another library B. So, the 2 dependencies of A only > differ in the minor version. > When I build/install this project only the 3.2.1-SNAPSHOT version of > library A gets downloaded. > Is this correct behaviour for maven since it evaluates the 3.2.1-SNAPSHOT > to be compatible with the 3.2.0 release version or should maven download > the 3.2.0 release version since it is explicit mentioned as a transient > dependency in the pom of a library B? >
