Hi Robert, just wanted to share. I came up with a nice algorithm :-) I do a
dryrun before I run release:branch and after the release:branch, i delete
the POM and rename POM.xml.branch to POM.xml and commit.
--
View this message in context:
http://maven.40175.n5.nabble.com/mvn-release-branch-upd
Thanks Robert. We currently use Maven 2.0.10. I appreciate your help. I'm
totally new with the tool.
--
View this message in context:
http://maven.40175.n5.nabble.com/mvn-release-branch-updating-POM-incorrectly-tp5811978p5812320.html
Sent from the Maven - Users mailing list archive at Nabble.c
Good day Robert,
I wondered if you might be aware of a plugin that I can use to update the
scm connection? Then I can create the branch with mvn release:branch and
after that is complete I can update the connection with another command. I'm
trying to script a release. Some of the jars require mave
Thank you Robert. I'm not using the latest maven release. Using 2.0.10. Will
upgrade.
--
View this message in context:
http://maven.40175.n5.nabble.com/mvn-release-branch-updating-POM-incorrectly-tp5811978p5812022.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
Good day,
I hope someone can assist. I have posted something, but did not get any
reply. When running the release:branch, my branch gets created, but my scn
connection url in the trunk POM is not updating to point to the new branch's
URL.
I tried to pinpoint the problem. I opened the POM in notep
Good day,
I hope someone can assist. Running mvn release:branch -Dbranchname=foo . The
problem is that my POM file's SCM connection does not always update to point
to my new branch.
I ran this command a few times with different branch names. Sometimes the
SCM connection updates, other times not.
