Re: LATEST and RELEASE release version management
sounds like you want version ranges [1.0,2.0-!) Sent from my [rhymes with myPod] ;-) On 8 Apr 2009, at 01:39, Tim che...@gmail.com wrote: http://jira.codehaus.org/browse/MNG-4089 I need to read over the bug that was linked as a duplicate more closely but I don't think it's the same thing. What I asked for was the same as what you said with 1.0-LATEST. Doing something like that or 1.0-RELEASE would actually be very beneficial to people that know that minor releases won't break backwards compatibility but will allow for more features without having to keep changing versions. On Mon, Apr 6, 2009 at 6:29 PM, Brian E. Fox bri...@reply.infinity.nuwrote: Having the release plugin translate these values at release time _before_ 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 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 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 time. These builds would be reproducible because the release plugin tags the poms during the release process. I think what you're saying is that the build prior to the release build is not guaranteed to have the same dependent artifacts as the release build. I care about the release build being reproducible. Pete -- Emo Philips http://www.brainyquote.com/quotes/authors/e/emo_philips.html - A computer once beat me at chess, but it was no match for me at kick boxing. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: LATEST and RELEASE release version management
Version ranges seem to totally break reproducibility of released builds. Personally, I'd like to see these eliminated from Maven altogether and replaced with a separate version compatibility field that indicates which versions of a dependency you are compatible with but still have a specific version that you declare: ... dependency groupIdorg.springframework/groupId artifactIdspring-core/artifactId version2.5.5/version compatibility[2.5,3.0-!)/compatibility /dependency ... This would ensure reproducibility while providing higher value version information that could then be used 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 sounds like you want version ranges [1.0,2.0-!) Sent from my [rhymes with myPod] ;-) On 8 Apr 2009, at 01:39, Tim che...@gmail.com wrote: http://jira.codehaus.org/browse/MNG-4089 I need to read over the bug that was linked as a duplicate more closely but I don't think it's the same thing. What I asked for was the same as what you said with 1.0-LATEST. Doing something like that or 1.0-RELEASE would actually be very beneficial to people that know that minor releases won't break backwards compatibility but will allow for more features without having to keep changing versions. On Mon, Apr 6, 2009 at 6:29 PM, Brian E. Fox bri...@reply.infinity.nuwrote: Having the release plugin translate these values at release time _before_ 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 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 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 time. These builds would be reproducible because the release plugin tags the poms during the release process. I think what you're saying is that the build prior to the release build is not guaranteed to have the same dependent artifacts as the release build. I care about the release build being reproducible. Pete -- Emo Philips http://www.brainyquote.com/quotes/authors/e/emo_philips.html - A computer once beat me at chess, but it was no match for me at kick boxing. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: LATEST and RELEASE release version management
It does but that actually includes all SNAPSHOT versions. If you aren't interested in snapshot versions as well that that will break. On Wed, Apr 8, 2009 at 2:16 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: sounds like you want version ranges [1.0,2.0-!) Sent from my [rhymes with myPod] ;-) On 8 Apr 2009, at 01:39, Tim che...@gmail.com wrote: http://jira.codehaus.org/browse/MNG-4089 I need to read over the bug that was linked as a duplicate more closely but I don't think it's the same thing. What I asked for was the same as what you said with 1.0-LATEST. Doing something like that or 1.0-RELEASE would actually be very beneficial to people that know that minor releases won't break backwards compatibility but will allow for more features without having to keep changing versions. On Mon, Apr 6, 2009 at 6:29 PM, Brian E. Fox bri...@reply.infinity.nu wrote: Having the release plugin translate these values at release time _before_ 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 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 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 time. These builds would be reproducible because the release plugin tags the poms during the release process. I think what you're saying is that the build prior to the release build is not guaranteed to have the same dependent artifacts as the release build. I care about the release build being reproducible. Pete -- Emo Philips http://www.brainyquote.com/quotes/authors/e/emo_philips.html - A computer once beat me at chess, but it was no match for me at kick boxing. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Fred Allen http://www.brainyquote.com/quotes/authors/f/fred_allen.html - Washington is no place for a good actor. The competition from bad actors is too great.
Re: LATEST and RELEASE release version management
http://jira.codehaus.org/browse/MNG-4089 I need to read over the bug that was linked as a duplicate more closely but I don't think it's the same thing. What I asked for was the same as what you said with 1.0-LATEST. Doing something like that or 1.0-RELEASE would actually be very beneficial to people that know that minor releases won't break backwards compatibility but will allow for more features without having to keep changing versions. On Mon, Apr 6, 2009 at 6:29 PM, Brian E. Fox bri...@reply.infinity.nuwrote: Having the release plugin translate these values at release time _before_ 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 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 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 time. These builds would be reproducible because the release plugin tags the poms during the release process. I think what you're saying is that the build prior to the release build is not guaranteed to have the same dependent artifacts as the release build. I care about the release build being reproducible. Pete -- Emo Philips http://www.brainyquote.com/quotes/authors/e/emo_philips.html - A computer once beat me at chess, but it was no match for me at kick boxing.
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 released. We don't mind doing the releases, but the manual version update -- release -- revert version cycle is a chore. I was hoping that Maven could simplify this by allowing a project to declare a dependency on LATEST or 1.0-LATEST and have the maven release plugin resolve this to the actual latest released version available in the repository. The subsequent fully resolved pom would then be uploaded to the internal repository and the pom left in source control still references LATEST. Does maven already support something like this or would others find this useful? Peter Hayes Architecture Shared Technology Services | Fidelity Investments Management Technology
Re: LATEST and RELEASE release version management
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 that also have to be released. We don't mind doing the releases, but the manual version update -- release -- revert version cycle is a chore. I was hoping that Maven could simplify this by allowing a project to declare a dependency on LATEST or 1.0-LATEST and have the maven release plugin resolve this to the actual latest released version available in the repository. The subsequent fully resolved pom would then be uploaded to the internal repository and the pom left in source control still references LATEST. Does maven already support something like this or would others find this useful? Having a LATEST concept would be very useful for something like continuous integration builds, where the desire is for a project to depend on the latest version of another project (release or snapshot), rather than a specific version of another project, so that you can see what errors have been introduced or that should be allowed for. 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 the build to be repeatable. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
RE: LATEST and RELEASE release version management
rtf1uqccPrltQ.rtf Description: RTF file smime.p7s Description: S/MIME cryptographic signature
Re: LATEST and RELEASE release version management
If you are prepared to run maven multiple times as part of your CI build you could achieve some of what you are looking for with the versions-maven-plugin. step 1. use versions-maven-plugin to update the pom to the latest releases of all dependencies step 2. use maven-scm-plugin to commit the modified poms back to scm step 3. use maven-release-plugin to release the ci build (the following 2 steps are optional) step 4. use versions-maven-plugin to update the pom to the next snapshots of all dependencies step 5 . use maven-scm-plugin to commit the modified poms back to scm ok, so you're ci build will auto-generate tags... but if you root ci generated tags in a special ci-tags directory and only do these 3/5 step builds nightlly it should be less of an SCM churn -Stephen 2009/4/6 Hayes, Peter peter.ha...@fmr.com 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 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 time. These builds would be reproducible because the release plugin tags the poms during the release process. I think what you're saying is that the build prior to the release build is not guaranteed to have the same dependent artifacts as the release build. I care about the release build being reproducible. Pete
RE: LATEST and RELEASE release version management
Having the release plugin translate these values at release time _before_ 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 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 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 time. These builds would be reproducible because the release plugin tags the poms during the release process. I think what you're saying is that the build prior to the release build is not guaranteed to have the same dependent artifacts as the release build. I care about the release build being reproducible. Pete
Re: LATEST and RELEASE
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
RE: LATEST and RELEASE
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LATEST and RELEASE
Baptiste, I will try a new sample on my configuration and let you know the result so I can send the projects to the Maven community. I am using 2.0.9 also. Regards Jeff MAURY 2008/11/23 Baptiste MATHUS [EMAIL PROTECTED] I just checked it again. Both work... I tried running dependency:purge-local-repository before my dependency:tree and it always seems to work, which actually matches my past experience of the subject. Am I the only one to find it functional? Cheers. Le 23 novembre 2008 17:28, Jeff MAURY [EMAIL PROTECTED] a écrit : Are those artifacts resolved using your local repository or a remote repository ? Regards Jeff MAURY 2008/11/23 Baptiste MATHUS [EMAIL PROTECTED] I just checked it out again. We have a blank project that depends on another one with RELEASE version, it gave me 2.2.1.alpha01. I just switched to LATEST and it gave me 2.2.1.alpha02-SNAPSHOT. So, it works, at least for me. I'm using maven 2.0.9. Cheers. Le 23 novembre 2008 11:50, Jeff MAURY [EMAIL PROTECTED] a écrit : On Sat, Nov 22, 2008 at 10:51 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Well, I guess it's simpler than that. And reading the book chapter confirm what I already saw when using those keywords on my pom.xml in the past. * LATEST will just the latest available version, including snapshots * RELEASE will do exactly the same, excluding snapshots. Do you confirm you used LATEST ? I did and it didn't work on non-plugins artifacts. Regards Jeff MAURY Cheers. Le 21 novembre 2008 22:16, Jeff MAURY [EMAIL PROTECTED] a écrit : 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 [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 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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
Re: LATEST and RELEASE
On Sat, Nov 22, 2008 at 10:51 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Well, I guess it's simpler than that. And reading the book chapter confirm what I already saw when using those keywords on my pom.xml in the past. * LATEST will just the latest available version, including snapshots * RELEASE will do exactly the same, excluding snapshots. Do you confirm you used LATEST ? I did and it didn't work on non-plugins artifacts. Regards Jeff MAURY Cheers. Le 21 novembre 2008 22:16, Jeff MAURY [EMAIL PROTECTED] a écrit : 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 [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 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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_oCsh7CepKPaPTAhl=en
Re: LATEST and RELEASE
I just checked it out again. We have a blank project that depends on another one with RELEASE version, it gave me 2.2.1.alpha01. I just switched to LATEST and it gave me 2.2.1.alpha02-SNAPSHOT. So, it works, at least for me. I'm using maven 2.0.9. Cheers. Le 23 novembre 2008 11:50, Jeff MAURY [EMAIL PROTECTED] a écrit : On Sat, Nov 22, 2008 at 10:51 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Well, I guess it's simpler than that. And reading the book chapter confirm what I already saw when using those keywords on my pom.xml in the past. * LATEST will just the latest available version, including snapshots * RELEASE will do exactly the same, excluding snapshots. Do you confirm you used LATEST ? I did and it didn't work on non-plugins artifacts. Regards Jeff MAURY Cheers. Le 21 novembre 2008 22:16, Jeff MAURY [EMAIL PROTECTED] a écrit : 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 [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 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: LATEST and RELEASE
Are those artifacts resolved using your local repository or a remote repository ? Regards Jeff MAURY 2008/11/23 Baptiste MATHUS [EMAIL PROTECTED] I just checked it out again. We have a blank project that depends on another one with RELEASE version, it gave me 2.2.1.alpha01. I just switched to LATEST and it gave me 2.2.1.alpha02-SNAPSHOT. So, it works, at least for me. I'm using maven 2.0.9. Cheers. Le 23 novembre 2008 11:50, Jeff MAURY [EMAIL PROTECTED] a écrit : On Sat, Nov 22, 2008 at 10:51 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Well, I guess it's simpler than that. And reading the book chapter confirm what I already saw when using those keywords on my pom.xml in the past. * LATEST will just the latest available version, including snapshots * RELEASE will do exactly the same, excluding snapshots. Do you confirm you used LATEST ? I did and it didn't work on non-plugins artifacts. Regards Jeff MAURY Cheers. Le 21 novembre 2008 22:16, Jeff MAURY [EMAIL PROTECTED] a écrit : 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 [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 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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_oCsh7CepKPaPTAhl=en
Re: LATEST and RELEASE
I just checked it again. Both work... I tried running dependency:purge-local-repository before my dependency:tree and it always seems to work, which actually matches my past experience of the subject. Am I the only one to find it functional? Cheers. Le 23 novembre 2008 17:28, Jeff MAURY [EMAIL PROTECTED] a écrit : Are those artifacts resolved using your local repository or a remote repository ? Regards Jeff MAURY 2008/11/23 Baptiste MATHUS [EMAIL PROTECTED] I just checked it out again. We have a blank project that depends on another one with RELEASE version, it gave me 2.2.1.alpha01. I just switched to LATEST and it gave me 2.2.1.alpha02-SNAPSHOT. So, it works, at least for me. I'm using maven 2.0.9. Cheers. Le 23 novembre 2008 11:50, Jeff MAURY [EMAIL PROTECTED] a écrit : On Sat, Nov 22, 2008 at 10:51 PM, Baptiste MATHUS [EMAIL PROTECTED] wrote: Well, I guess it's simpler than that. And reading the book chapter confirm what I already saw when using those keywords on my pom.xml in the past. * LATEST will just the latest available version, including snapshots * RELEASE will do exactly the same, excluding snapshots. Do you confirm you used LATEST ? I did and it didn't work on non-plugins artifacts. Regards Jeff MAURY Cheers. Le 21 novembre 2008 22:16, Jeff MAURY [EMAIL PROTECTED] a écrit : 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 [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 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: LATEST and RELEASE
Well, I guess it's simpler than that. And reading the book chapter confirm what I already saw when using those keywords on my pom.xml in the past. * LATEST will just the latest available version, including snapshots * RELEASE will do exactly the same, excluding snapshots. Cheers. Le 21 novembre 2008 22:16, Jeff MAURY [EMAIL PROTECTED] a écrit : 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 [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 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_oCsh7CepKPaPTAhl=en -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
LATEST and RELEASE
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?
Re: LATEST and RELEASE
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [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 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_oCsh7CepKPaPTAhl=en
Re: LATEST and RELEASE
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/maven-book/reference/pom-relationships.html#d0e9801 Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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_oCsh7CepKPaPTAhl=en
RE: LATEST and RELEASE
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 first I need to fix somethings it seems. You also made me go look in the metadata.xml and it turns out our qualifiers or our build process might be messing things up. I have to check if we're using deploy or install too (if install what we use for -DupdateReleaseInfo= I'm guess it's not set). The metadata version hasn't changed in 5 releases. By chance have you used it for parent version? We're planning to put a real version in as late (late binding) as possible using a custom release plugin to save the dev's from the hassle updating a couple of hundered projects everytime we do something to the corporate build pom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LATEST and RELEASE
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 PROTECTED]wrote: 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 first I need to fix somethings it seems. You also made me go look in the metadata.xml and it turns out our qualifiers or our build process might be messing things up. I have to check if we're using deploy or install too (if install what we use for -DupdateReleaseInfo= I'm guess it's not set). The metadata version hasn't changed in 5 releases. By chance have you used it for parent version? We're planning to put a real version in as late (late binding) as possible using a custom release plugin to save the dev's from the hassle updating a couple of hundered projects everytime we do something to the corporate build pom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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_oCsh7CepKPaPTAhl=en
