Thank you Stephen. Are there any other ways to stabilize my dependencies then?
i have > 300 poms all depending on the released+1 development version. This must be a common use-case when using RCs, no? you increase all your versions to your next RC-2-SNAPSHOT as soon as you create your RC-1, but if that RC-1 happens to be released, then all your poms will be depending on the SNAPSHOT of an RC-2 that will never be made so you have to "downgrade" your dependency versions Am I doing something out of the ordinary here? Alejandro Endo | Software Designer/Concepteur de logiciels From: Stephen Connolly <stephen.alan.conno...@gmail.com> To: Maven Users List <users@maven.apache.org>, Date: 2014-01-20 12:34 Subject: Re: versions maven plugin v-m-p does not roll back version numbers On 20 January 2014 16:59, <alejandro.e...@miranda.com> wrote: > Not sure if this is the right list for codehaus plugins. If not I > apologize > > I have a pom with this > > <dependencies> > <dependency> > <groupId>foo.blah</groupId> > <artifactId>bar</artifactId> > <version>1.2.0-RC-7-SNAPSHOT</version> > </dependency> > </dependencies> > > I want to run the versions plugin to replace 1.2.0-RC-7-SNAPSHOT with the > version we actually released of the code, which is 1.2.0-RC-6. Looking at > the available mojos, it seems like versions:use-latest-releases is the > right one to use. In the matrix here it says that this goal will modify > -SNAPSHOT dependencies. Well, it doesn't. If i instead set the version to > 1.2.0-RC-3 (no snapshot), the mojo does update the dependency to > 1.2.0-RC-6 so I don't know if this is just the documentation being wrong. > I also tried use-latest-versions without success > > Any idea how to do this? I just want to change the dependencies (which are > currently SNAPSHOT due to the m-release-p) to the latest released versions > > Thank you, > Alejandro Endo | Software Designer/Concepteur de logiciels > > DISCLAIMER: > Privileged and/or Confidential information may be contained in this > message. If you are not the addressee of this message, you may not > copy, use or deliver this message to anyone. In such event, you > should destroy the message and kindly notify the sender by reply > e-mail. It is understood that opinions or conclusions that do not > relate to the official business of the company are neither given > nor endorsed by the company. > Thank You. > DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
