MRELEASE-484 and 485 say that I was using 2.0-beta-10 when I gave up. On Fri, Oct 23, 2009 at 10:10 PM, Matt Milliss <[email protected]>wrote:
> I've been trying to solve this exact same problem, it looks like a bug in > the release plugin, what version are you using. > > > On 15/10/2009 7:40 AM, Allan Ditzel wrote: > >> Really? Were you running it from the location the trunk was checked out? >> For >> us, if we do a mvn release:prepare in the location of the trunk, then >> release:perform, and then cd into target/checkout and from there do mvn >> release:branch -DbranchName=my-branch -DupdateBranchVersions=true >> -DupdateWorkingCopyVersions=false (interactive mode) then we're able to >> branch without many problems. Also, if we do an svn co of a tag url and >> then >> do mvn release:branch (as before) from the directory the tag was checked >> out >> then it also works. >> >> It only gives us problem when we use it in batch mode. >> >> On Wed, Oct 14, 2009 at 4:23 PM, Benson Margulies<[email protected] >> >wrote: >> >> >> >>> personally, I couldn' t get release:branch to work at all, interactively >>> or >>> batch. >>> >>> On Wed, Oct 14, 2009 at 2:23 PM, Allan Ditzel<[email protected] >>> >>> >>>> wrote: >>>> >>>> >>> >>> >>>> Hi, >>>> >>>> I'm trying to make a branch from a tag in batch mode using the release >>>> plugin. The pom in the tag has its version set to 0.2.0. I would like >>>> for >>>> the branch version to be 0.2.1-SNAPSHOT, however when I use the plugin >>>> it >>>> always sets the branch version to 0.2.0-SNAPSHOT. However, in >>>> interactive >>>> mode I'm able to create the branch correctly. Here is the command I am >>>> executing: >>>> >>>> mvn -B release:branch -DbranchName=testBranch-0.2.X >>>> -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false >>>> -Dproject.rel.test.release_management:test-project=0.2.1 -Ptestprofile >>>> >>>> I have also tried: >>>> >>>> mvn -B release:branch -DbranchName=testBranch-0.2.X >>>> -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false >>>> -Dproject.dev.test.release_management:test-project=0.2.1 -Ptestprofile >>>> >>>> and >>>> >>>> mvn -B release:branch -DbranchName=testBranch-0.2.X >>>> -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false >>>> -Dproject.dev.test.release_management:test-project=0.2.1-SNAPSHOT >>>> -Ptestprofile >>>> >>>> They all yield a pom in the branch with its version set to >>>> >>>> >>> 0.2.0-SNAPSHOT. >>> >>> >>>> Does anyone have any ideas? >>>> >>>> Thanks, >>>> >>>> Allan >>>> >>>> >>>> >>> >>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
