Re: understanding maven version resolution: minor and snapshots

2017-04-22 Thread Erik Bertelsen
Also: The command mvn dependency:tree may be your rescue, look for entries marked as conflicting. - Erik 2017-04-22 9:31 GMT+02:00 Anders Hammar : >> Nope it pick the *nearest* version. >> > >> Direct dependency trumps transitive >> > > And to give the full picture, if

Re: understanding maven version resolution: minor and snapshots

2017-04-22 Thread Anders Hammar
> Nope it pick the *nearest* version. > > Direct dependency trumps transitive > And to give the full picture, if different versions are declared at the same level in the dependency tree (typically via transitive dependencies when you don't have a direct dep), the first declaration wins. So, the

Re: understanding maven version resolution: minor and snapshots

2017-04-22 Thread Stephen Connolly
On Sat 22 Apr 2017 at 00:21, Curtis Rueden wrote: > 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

Re: understanding maven version resolution: minor and snapshots

2017-04-21 Thread Curtis Rueden
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