You can also use the Maven Release Plugin update-versions mojo: http://maven.apache.org/plugins/maven-release-plugin/update-versions-mojo.html
On Fri, Aug 27, 2010 at 4:00 PM, Anders Hammar <[email protected]> wrote: > Just a comment regarding your example. I'm assuming that the actual > "release" (the final one) will be 1.4, right? And that you're thinking that > you will be releasing some kind of milestone called 1.4-pre-1, right? > In that case, I would still call the development version 1.4-SNAPSHOT all > the way until you release the final 1.4 release. During the course, you > decide to release stable milestones (or whatever you want of call them, > they > are maven releases anyway) such as 1.4-pre-1, 1.4-pre-2, etc. Then just cut > a release from the 1.4-SNAPSHOT lane that you give the version 1.4-pre-1. > The developement version continues to be called 1.4-SNAPSHOT after that. > Maybe someone else can comment on this approach, but I find it good as the > ones that want to use the latest snapshots don't have to worry about if > they > should use 1.4-pre-1-SNAPSHOT, 1.4-pre-2-SNAPSHOT, or similar. They just > specify 1.4-SNAPSHOT and always get the latest from that lane. While the > ones that specifically want to use/try a milestone release use that version > (e.g. 1.4-pre-1). > Another benefit is that you don't have to decide on this milestone release > in advance (as you don't use their specific version number in the snapshot > version), but can cut them as you like. Maybe you cut them every night by > your CI, or every Sunday? > > /Anders > On Thu, Aug 26, 2010 at 17:23, C. Benson Manica <[email protected]> > wrote: > > > What is the "proper" way to update the development version of a project > > (and > > its subprojects if any)? Say a project is currently at 1.4-SNAPSHOT but > I > > decide I want to mark it as 1.4-pre-1-SNAPSHOT - is there a way to do > that > > without manually editing all the poms involved? > > > > -- > > C. Benson Manica > > [email protected] > > >
