it was designed for plugins only and it is less usefull than you think
it also depends on the correct metadata being deployed if you deploy in the following order, the following versions 1.0 2.0 2.1 3.0 1.1 then LATEST will be 1.1 it also gives an irreproducible build, as tomorrow you could end up picking up 3.1 or 4.0 or 2.2 or 1.2 depending on what gets published version ranges are more reliable (but again these require correct metadata and give you an irreproducible build) the problem you *think* you have is actually not a problem, and if you use the release plugin [and perhaps additionally the versions plugin] everything will "just work out" -Stephen On Saturday, July 4, 2009, Jaikiran <[email protected]> wrote: > > Infact i get an error when i use LATEST: > > 1) org.myapp.abc:myapp-core:jar:LATEST > > Try downloading the file manually from the project website. > > .... > > Seems like LATEST isn't recognized as a valid qualifier? > > > > Jaikiran wrote: >> >> I am reading the Maven definitive guide >> http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html >> which says: >> >> "LATEST refers to the latest released or snapshot version of a particular >> artifact..." >> >> Does this really work? I am using LATEST against a artifact, but i don't >> seem to get it to use the latest available "snapshot" for that artifact. >> It seems to look for the latest "released" artifact. I am using Maven >> 2.0.9 >> >> >> > > -- > View this message in context: > http://www.nabble.com/LATEST-version-of-an-%22artifact%22-tp24335281p24335445.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
