I guess I was wrong...it *did* screw up my tagged code.  Now, I have to
figure out how badly and get that all fixed, too.

Why would the release:branch goal put changes back into the source tree?

David C. Hicks wrote:
> Hi gang,
>
> I need to branch from a prior release tag to fix a defect.  I thought I
> had the right "process," but something is not happy.  We do have the
> project enabled for the maven-release-plugin.  Here are the steps I took:
>
> 1) Check code out of SVN from the previous release tag.
> 2) Using release:branch -  mvn -DbranchName=Salient-0.9.22.1
> -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false release:branch
> 3) Enter my version label when prompted "0.9.22.1-SNAPSHOT" (repeat for
> each sub-module [i couldn't get autoVersionSubmodules to play nice])
> 4) Get an error:
>
> svn: Commit failed (details follow):
> svn: Source url
> 'svn://svn.enttek.com/allureglobal/dm/tags/salient-0.9.22' is from
> different repository
>
> Now, it's true that the SCM information in the POM gets updated such
> that it isn't the same as where the code was checked out from, but that
> shouldn't matter, should it?  We're not going to modify the original
> sources - we're just creating the branch.  Right?
>
> Maybe I'm going about this all wrong, but I didn't find much in the way
> of documents/blogs/stories on Google - at least, nothing that shed any
> light on this for me.
>
> Thanks,
> Dave
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to