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.alan.conno...@gmail.com] Sent: 22 September 2009 20:31 To: Maven Users List Cc: <users@maven.apache.org> 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 in progress... 1.x and 2.x as each stream deploys their releases, RELEASE will jump back and forth between the two versions... 1.1, 2.1, 1.2, 1.3, 2.2, 1.4, 2.3, 1.1.1, etc not what you want... LATEST plays the same way, only with -SNAPSHOTs added into the mix, so now your CI server redeploying the latest -SNAPSHOTs after each commit makes everyone scream usually what you want is version ranges, or (plug) use versions-maven- plugin to update versions for you in a mire controlled manor than version ranges allow (the issue with version ranges is you cannot exclude an intermediate - SNAPSHOT from creaping in to any range... but then sometimes, ie during development, that is exactly what you want!) Sent from my [rhymes with tryPod] ;-) On 22 Sep 2009, at 20:03, <james.sh...@nomura.com> wrote: > 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 to > work and just tries looking for a version with the explicit name > LATEST > rather than using the repo's metadata. > > > > I don't see the concept of LATEST or RELEASE mentioned anywhere in the > official Maven docs though > (http://maven.apache.org/guides/introduction/introduction-to-dependency- > mechanism.html) > > > > Is this functionality actually in 2.0.9 or was it dropped (or indeed > added in a later version)? Afraid the FAQs and Google aren't > turning up > any conclusive information either way > > > > Thanks > > > > James > > > > > > > This e-mail (including any attachments) is confidential, may contain > proprietary or privileged information and is intended for the named > recipient(s) only. Unintended recipients are prohibited from taking > action > on the basis of information in this e-mail and must delete all copies. > Nomura will not accept responsibility or liability for the accuracy or > completeness of, or the presence of any virus or disabling code in, > this > e-mail. If verification is sought please request a hard copy. Any > reference > to the terms of executed transactions should be treated as > preliminary only > and subject to formal written confirmation by Nomura. Nomura > reserves the > right to monitor e-mail communications through its networks (in > accordance > with applicable laws). No confidentiality or privilege is waived or > lost by > Nomura by any mistransmission of this e-mail. Any reference to > "Nomura" is > a reference to any entity in the Nomura Holdings, Inc. group. Please > read > our Electronic Communications Legal Notice which forms part of this > e-mail: > http://www.Nomura.com/email_disclaimer.htm > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This e-mail (including any attachments) is confidential, may contain proprietary or privileged information and is intended for the named recipient(s) only. Unintended recipients are prohibited from taking action on the basis of information in this e-mail and must delete all copies. Nomura will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in, this e-mail. If verification is sought please request a hard copy. Any reference to the terms of executed transactions should be treated as preliminary only and subject to formal written confirmation by Nomura. Nomura reserves the right to monitor e-mail communications through its networks (in accordance with applicable laws). No confidentiality or privilege is waived or lost by Nomura by any mistransmission of this e-mail. Any reference to "Nomura" is a reference to any entity in the Nomura Holdings, Inc. group. Please read our Electronic Communications Legal Notice which forms part of this e-mail: http://www.Nomura.com/email_disclaimer.htm --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
