True... provided your scm system supports all that ;-) In most cases it should work.
On Mon, January 14, 2013 9:38 am, Nick Stolwijk wrote: > Or take a look at the Maven Release Plugin - branch goal [1] and it's > documentation page [2]. > > [1] > http://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html > [2] > http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html > > Hth, > > Nick Stolwijk > > ~~~ Try to leave this world a little better than you found it and, when > your turn comes to die, you can die happy in feeling that at any rate you > have not wasted your time but have done your best ~~~ > > Lord Baden-Powell > > > On Mon, Jan 14, 2013 at 6:23 PM, Manfred Moser <manf...@mosabuam.com> > wrote: > >> The mvn versions plugin can do the update of the pom... but the >> branching >> and stuff can be done with the scm plugin. >> >> If you want it completely automated you have to roll those together on >> your own somehow. >> >> On Mon, January 14, 2013 9:06 am, John Kramer wrote: >> > Are there any automated tools for that or should I write my own >> > see/perl/something? >> > >> > John Kramer >> > email: jkra...@mojiva.com >> > mobile: 314.435.2370 >> > skype: kramer.mojiva >> > twitter: @KramerKnowsTech <https://twitter.com/KramerKnowsTech> >> > 0xCAFEBABE00000032 >> > >> > >> > >> > >> > >> > >> > >> > On 1/14/13 11:43 AM, "Manfred Moser" <manf...@mosabuam.com> wrote: >> > >> >>A very common and well working approach is to have a branch qualifier >> in >> >>the version and change the version of your project with the versions >> >>plugin. >> >> >> >>So e.g. you would have >> >> >> >>1.1.2-brancha-SNASPHOT >> >>1.1.2-branchb-SNASPHOT >> >> >> >>and to update them after you cut the branch in your scm you could use >> >> >> >>mvn versions:set -=DnewVersion= 1.1.2-brancha-SNAPSHOT >> >> >> >>manfred >> >> >> >> >> >>On Mon, January 14, 2013 8:39 am, John Kramer wrote: >> >>> Hi guys, >> >>> >> >>> Please forgive me if this seems like a newbie question. >> >>> >> >>> >> >>> I am reasonably seasoned with Maven, but have never really handle >> >>> branching myself, and now I am put in the position where I am going >> to >> >>> have to. I.e. What I am asking here is when I branch in git (or >> svn >> >>> or >> >>> whatever) how do I manage versions in poms (and any other versions I >> am >> >>> not thinking about)? >> >>> >> >>> >> >>> Could someone point me at best practices for branches? >> >>> >> >>> Thanks! >> >>> >> >>> >> >>> John Kramer >> >>> email: jkra...@mojiva.com<mailto:jkra...@mojiva.com> >> >>> mobile: 314.435.2370 >> >>> skype: kramer.mojiva >> >>> twitter: @KramerKnowsTech<https://twitter.com/KramerKnowsTech> >> >>> 0xCAFEBABE00000032 >> >>> >> >>> >> >> >> >> >> >>--------------------------------------------------------------------- >> >>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 >> > >> >> >> --------------------------------------------------------------------- >> 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
