You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Jeff MAURY <je...@jeffmaury.com> on 2008/11/21 22:16:50 UTC

Re: LATEST and RELEASE

>From my experience, using RELEASE as a version identifier works for any
kinds of artifacts given the fact that you should have install or deployed
the artifact using the parameter updateReleaseInfo to true.
Using the LATEST version identifier is available only for Maven plugins, not
for standards artifacts, because the artifact metadata needs to store this
information and this is only possible through the maven plugin plugin.

Regards
Jeff MAURY

On Fri, Nov 21, 2008 at 10:04 PM, Timothy Reilly <tr...@prolifics.com>wrote:

> I thought I these two keywords LATEST and RELEASE were supported
> versions that could be used in a pom.xml.
>
> Does anyone know more about them, an I mistaken?
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.lastfm.fr/listen/user/jeffmaury/personal
Mes CDs à récupérer:
http://spreadsheets.google.com/ccc?key=pNeg4Doa_oCsh7CepKPaPTA&hl=en

Re: LATEST and RELEASE

Posted by Baptiste MATHUS <ml...@batmat.net>.

I guess this could be related, but we almost never use install. Actually,
for the LATEST use case, we just commit and have a continuous integration
serverthat will just push the resulting artifact to the corporate maven
repository (and it will usually be downloaded some minutes after thanks to
m2e when asking to "update snapshots"/"update dependencies").

For RELEASE, that's almost the same: they are deployed on one machine and
mainly download via the repo by everybody else. Maybe dowloading will
correctly set the metadata contrary to mvn install?

Cheers.

2008/12/3 Timothy Reilly <tr...@prolifics.com>

> Just an observation from today when RELEASE didn't work for us.
>
> I was at someone's desk who normally build's the parent pom we are
> trying to reference as RELEASE. His last build of the pom or perhaps
> every build to his local repository is done without mvn install
> -DupdateReleaseInfo=true (so false.) The dependent project failed to
> build due to not resolving the RELEASE version. He rebuilt the parent
> (corporate pom) with -DupdateReleaseInfo=true and then it worked.
>
> My guess is that when RELEASE version is being resolved it finds the
> artifact in the local repository but doesn't find the release metadata
> and fails.
> Perhaps, while resolving RELEASE all configured repositories need or
> should be consulted... Seems like that doesn't happen. (first find fail)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !