, Peter [mailto:peter.ha...@fmr.com]
Sent: Monday, April 06, 2009 12:12 PM
To: Maven Users List
Subject: RE: LATEST and RELEASE release version management
Graham Leggett wrote:
Having said that, it makes no sense to have the release plugin care
about LATEST, because by definition, building
within metadata and leveraged by
containers such as OSGI.
Pete
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Wednesday, April 08, 2009 3:16 AM
To: Maven Users List
Cc: Maven Users List
Subject: Re: LATEST and RELEASE release version management
PM
To: Maven Users List
Subject: RE: LATEST and RELEASE release version management
Graham Leggett wrote:
Having said that, it makes no sense to have the release plugin care
about LATEST, because by definition, building against LATEST isn't
repeatable, and in order
the validation build and tag is the only sane way to use them.
I currently have never use them because they aren't repeatable.
From: Hayes, Peter [mailto:peter.ha...@fmr.com]
Sent: Monday, April 06, 2009 12:12 PM
To: Maven Users List
Subject: RE: LATEST and RELEASE release version management
We use Maven in an enterprise environment and internally we are required
to execute release builds whenever we want to install to our testing
environment. We have found that executing many release builds can be
tedious when we have in-development snapshot dependencies that also have
to be
Hayes, Peter wrote:
We use Maven in an enterprise environment and internally we are required
to execute release builds whenever we want to install to our testing
environment. We have found that executing many release builds can be
tedious when we have in-development snapshot dependencies
rtf1uqccPrltQ.rtf
Description: RTF file
smime.p7s
Description: S/MIME cryptographic signature
the release plugin care
about LATEST, because by definition, building against LATEST isn't
repeatable, and in order for there to be a release, you need the build
to be repeatable.
I think this does impact the release plugin as it could offer the ability
to resolve the LATEST version at release
To: Maven Users List
Subject: RE: LATEST and RELEASE release version management
Graham Leggett wrote:
Having said that, it makes no sense to have the release plugin care
about LATEST, because by definition, building against LATEST isn't
repeatable, and in order for there to be a release, you need
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
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
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
[EMAIL PROTECTED]
wrote:
I thought I these two keywords LATEST and RELEASE were
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 [EMAIL PROTECTED]
wrote:
I thought I these two keywords LATEST and RELEASE were supported
versions that could be used
,
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
[EMAIL PROTECTED]
wrote:
I thought I these two keywords LATEST
through the maven plugin
plugin.
Regards
Jeff MAURY
On Fri, Nov 21, 2008 at 10:04 PM, Timothy Reilly
[EMAIL PROTECTED]
wrote:
I thought I these two keywords LATEST and RELEASE were supported
versions that could be used in a pom.xml.
Does anyone know
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
[EMAIL PROTECTED]
wrote:
I thought I these two keywords LATEST and RELEASE were
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
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?
I thought I these two keywords LATEST and RELEASE were supported
versions that could be used in a pom.xml.
9.3.1.3. LATEST and RELEASE Versions
http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0e9801
Wayne
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 [EMAIL PROTECTED]wrote:
I thought I these two keywords LATEST and RELEASE were supported
In my opinion, this chapter is bogus
Jeff MAURY
On Fri, Nov 21, 2008 at 10:18 PM, Wayne Fay [EMAIL PROTECTED] wrote:
I thought I these two keywords LATEST and RELEASE were supported
versions that could be used in a pom.xml.
9.3.1.3. LATEST and RELEASE Versions
http://books.sonatype.com
Jeff,
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.
Thanks. That's very helpful! I was about to complain it does not work -
but
If you intent to use it for you corporate parent pom, I think this should
work assumed you deploy or install it using the updateReleaseInfo to true
and refer the corporate parent pom using the RELEASE version.
Regards
Jeff MAURY
On Fri, Nov 21, 2008 at 10:55 PM, Timothy Reilly [EMAIL
23 matches
Mail list logo
