Those special values, AFAIK are for plugin versions only.... and are
depricated

2008/11/19 Todd Thiessen <[EMAIL PROTECTED]>

> Thanks for the reply. I do understand that SNAPSHOT is meant for
> developers only.  I did read here:
>
> http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0
> e9801<http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0e9801>
>
> that LATEST means the latest SNAPSHOT or RELEASED version and a version
> of RELEASED means the latest RELEASED version.  I tried playing with
> these as version values but the artifact couldn't be found.  I did have
> success using no upper bound on range however.
>
> I think my biggest confusion was the naming convension here. The term
> "SNAPSHOT" typically means a fixed state of something at a particular
> point in time. However, in Maven it isn't fixed at all. It is in
> constant flux. A better name for SNAPSHOT would of been something like
> LATEST-DEV.
>
>
> ---
> Todd Thiessen
>
> -----Original Message-----
> From: Simone Gianni [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 19, 2008 9:19 AM
> To: Maven Users List
> Subject: Re: specifying "latest" for a dependency
>
> Hi Todd,
> SNAPSHOT is different from latest, because a SNAPSHOT is unstable,
> pre-alpha stuff, not the latest known working released version. This is
> a critical distinction, many projects use and publish SNAPSHOTS for
> internal use (for example, if I have three modules, they all evolve
> simultaneously, so they depend on the snapshot of each other until we
> arrive to a release).
>
> To get the latest one, simply put no upper bound to a version range.
> This will avoid SNAPSHOTS, and get the highest available version. And
> yes, only the first three are considered numbers. Obviously this is not
> perfect, because every organization can setup a standard with one, two,
> three, four or one hundred numbers. Anyway the three numbers are quite
> considered a de-facto standard, and used in 90% of software development.
>
> So, I would suggest to stick with 3 (major, minor, rev) number, and use
> the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI
> timestamp), remembering that if your development practice often brings
> you to RC10 or above, you should number them 01, 02 etc...
>
> Simone
>
> Todd Thiessen wrote:
> > Snapshot versions work this way. Perhaps this is what you are looking
> > for.
> >
> > I was confused by this too btw. I think snapshot would of been better
> > named as "lastest".
> >
> > I don't know if you can do this with release versions though. It would
>
> > be nice to always get the latest release.
> >
> >
> > ---
> > Todd Thiessen
> >
> > -----Original Message-----
> > From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, November 18, 2008 12:31 PM
> > To: [email protected]
> > Subject: specifying "latest" for a dependency
> >
> > I know this has been discussed time and time again, but I can't seem
> > to combine the right google keywords to find what I'm looking for.
> >
> > How do you specify "latest" for a dependency?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Simone Gianni            CEO Semeru s.r.l.           Apache Committer
> http://www.simonegianni.it/
>
>
> ---------------------------------------------------------------------
> 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]
>
>

Reply via email to