@maven.apache.org
Subject: RE: LATEST / RELEASE dependency version
Thanks Stephen, that's very helpful - hadn't appreciated the subtle
difference that LATEST was not necessarily LARGEST.
Will take a good look at ranges then - thanks
-Original Message-
From: Stephen Connolly [mailto:stephen.
9 20:31
To: Maven Users List
Cc:
Subject: Re: LATEST / RELEASE dependency version
these are *deprecated* features
they never do what you think they do!
LATEST picks the last version to be deployed... RELEASE picks the last
non-SNAPSHOT to be deployed
now imagine you have two development streams i
these are *deprecated* features
they never do what you think they do!
LATEST picks the last version to be deployed... RELEASE picks the last
non-SNAPSHOT to be deployed
now imagine you have two development streams in progress... 1.x and 2.x
as each stream deploys their releases, RELEASE wil
fourni.
> Subject: LATEST / RELEASE dependency version
> Date: Tue, 22 Sep 2009 20:03:10 +0100
> From: james.sh...@nomura.com
> To: users@maven.apache.org
>
> Looking in the Sonatype Maven book I see mention of the ability to
> specify the version of a dependency as LATES
Looking in the Sonatype Maven book I see mention of the ability to
specify the version of a dependency as LATEST or RELEASE
(http://www.sonatype.com/books/maven-book/reference/pom-relationships-se
ct-pom-syntax.html , 9.3.1.3)
However when I try this (I'm using 2.0.9 and Nexus) it doesn't seem
