The release-plugin will replace a version n-SNAPSHOT with n, then tag this version n and replace it again with (n+1)-SNAPSHOT All those versions will be prompted, but prefilled as default.
so if you have a myproject-2.17-SNAPSHOT mvn release:prepare will create and tag a myproject-2.17 in the SCM. Essentially this turns your snapshot build into a full build! Afterwards, the version number will be increased to myproject-2.18-SNAPSHOT in the SCM automatically mvn release:perform will then deploy your tagged myproject-2.17 Btw, a SNAPSHOT version should almost never get to a non-private repo! LieGrü, strub --- Niranjan Deshpande <[EMAIL PROTECTED]> schrieb am Do, 5.6.2008: > Von: Niranjan Deshpande <[EMAIL PROTECTED]> > Betreff: Re: AW: modifying version number in POM > An: "Maven Users List" <[email protected]> > Datum: Donnerstag, 5. Juni 2008, 8:49 > Hi Chris, > > So you meant to say that SNAPSHOT will be repaced by a > timestamp at the run > time? > also, can we avoid the chekin of the pom and tagging of the > project that > happens after mvn release:prepare? i am rather > experimenting on things > and dnt want to invite the wrath of other developers if > ther repository is > contaminated ;) > > > On 6/5/08, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > > > Mark Struberg <[EMAIL PROTECTED]> wrote on > 04/06/2008 22:53:35: > > > > > Maybe i missed the point, or you did. > > > > > > The usual behaviour is to always have a SNAPSHOT > version in your SCM > > > e.g. <version>1.4-SNAPSHOT</version> > > > > > > If you make a build, you simply use the > maven-release-plugin > > > > > > $>mvn release:prepare > > > this will > > > .) ask you the release-version which will default > to 1.4 and the next- > > > version which defaults to 1.5-SNAPSHOT > > > .) does some usefull checks > > > .) checkin pom with the 1.4 into SCM and tag the > project > > > .) set the next version in the pom to > 1.5-SNAPSHOT or whatever you > > > provided in step 1 > > > > > > after this, do a > > > $>mvn release:perform > > > to build the project with the freshly tagged > build version > > > > > > So there is usually no need to set versions in > the pom manually. > > > > So long as maven supports your scm... > > > > -Chris > > > > > > > ********************************************************************** > > CAUTION - This message is intended for the addressee > named above. It may > > contain privileged or confidential information. > > > > If you are not the intended recipient of this message > you must: > > - Not use, copy, distribute or disclose it to anyone > other than the > > addressee; > > - Notify the sender via return email; and > > - Delete the message (and any related attachments) > from your computer > > immediately. > > > > Internet emails are not necessarily secure. Australian > Associated Motors > > Insurers Limited ABN 92 004 791 744 (AAMI), and its > related entities, do not > > accept responsibility for changes made to this message > after it was sent. > > > > Unless otherwise stated, views expressed within this > email are the author's > > own and do not represent those of AAMI. > > > ********************************************************************** > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > -- > Regards, > Niranjan Deshpande > > "Shut yourself from the world and create the reality > you want" __________________________________________________________ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
