I would highly recommend that you tag your projects X.Y and when you build branches introduce the .Z
maven treats the -SSS specially and makes it less e.g. X.Y.Z-A < X.Y.Z which obviously causes odd behaviour.. I use versions like 1.0, 1.1, 1.2 and patches being builds off branches being 1.0.1, 1.0.2, 1.1.2 etc etc On Wednesday 31 October 2007 02:33, Ionut Scutaru wrote: > Hi guys, > We have a multi-module project; we are using 1.0.0-SNAPSHOT as version for > every module. We are trying to have a release at the end of every week, so > our releases get the following form: 1.0.0-Wxx. In time we realized we need > to branch the project before releasing it so we have some time to fix the > critical issues that don't pass sanity testing. > > What we want to do is to create a branch on the release day and not the > release itself (this one will be released 2-3 days after the branch is > done). The version of the trunk needs to remain the same (e.g. > 1.0.0-SNAPSHOT) while the version of the branch needs to be changed to the > final version of the release (e.g. 1.0.0-Wxx). We tried to use mvn > release:branch to release a branch, but we are seeing an odd behavior: the > trunk's pom.xml files are modified as well - their version is changed to > the same one as the branch. This is hapening although we specify > -DupdateWorkingCopyVersions=false when we run the mvn release:branch > process. > > Here's the entire command line we are using: > mvn release:branch -DupdateBranchVersions=true > -DupdateWorkingCopyVersions=false -DautoVersionSubmodules=true > -DbranchName="Maven_Example_1.0.0" > > Is this a desired behavior or maybe we are using it incorrectly ? Can > anybody recommend a "best practice" for branching (in conjunction with > maven, of course) > > Thank you in advance. -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
