These are very dangerous versions to suggest use of.

These are deprecated and are only "special" versions when considering
plugins... and they do not behave as you think they behave.

LATEST is the last version to have been deployed, so if you have been
working on 2.0 and start doing some work on a hotfix to 1.1, i.e.
1.1-SNAPSHOT, then your CI server will deploy 1.1-SNAPSHOT and that will
become the LATEST

RELEASE is only slightly more stable... it will jump from 2.0 to 1.1 when
you release that 1.1-SNAPSHOT as 1.1

-Stephen

2009/10/15 Mark Struberg <[email protected]>

> Hi Gerhard!
>
> You can use
>
> <version>LATEST</version>
>
> to fetch the latest from the repositories (including snapshots) or
>
> <version>RELEASE</version>
>
> for the latest non-snapshot version.
> but use this with care!
> You should not be able to release a pom with such a dependency because the
> build is not reliable (at least should be, but never tried that behaviour of
> the release-plugin myself, anyone?)
>
> LieGrue,
> strub
>
>
>
> ----- Original Message ----
> > From: gerhard presser <[email protected]>
> > To: [email protected]
> > Sent: Thu, October 15, 2009 8:59:32 AM
> > Subject: fetching latest release of an artifact
> >
> >
> > hi all!
> > i'm writing a plugin which helps me to generate a cumulated patch file
> for
> > my
> > application.
> > because of that i want to fetch the last release of my artifact.
> > how can i do that. i'm playing around with ArtifactResolver,
> > ArtifactMetadataSource etc.
> > is this the right way?
> > regards
> > --
> > View this message in context:
> >
> http://www.nabble.com/fetching-latest-release-of-an-artifact-tp25903867p25903867.html
> > Sent from the Maven Developers 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]
>
>

Reply via email to