Actually it's working fine... I was able to do the branch, after many hours of pain...
The problem that I noticed is that , if there is even a small problem during the release:branch, I'm being left with all the changes commited in Subversion. Of course, mvn release:rollback doesn't work so I'm forced to make a manual rollback on subversion before going any further. (actually this is why it took me so much time) Does anybody if mvn release:rollback should work for the branch goal ? I faced so many problems during release:branch in a small, testing environment that makes me afraid of applying this procedure for our entire project. Guys, you really need to improve its reliability ... On 10/30/07, Ionut Scutaru <[EMAIL PROTECTED]> 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.
