Greetings Alex,
I met the same problem and so I googled Your question (m2, svn) yesterday.
Hi all,
I have a multi-module project that I'm trying to run the release
plugin >against.
scm connections are configured in the POMs and so is the tagBase.
Checkin of POMs with updated release numbers works, but the tagging
fails...
Strangely enough, I get prompted for the new release and development
numbers for all modules BUT I am only ever asked about the tag for the
root POM file.
...
The svn tag command failed.
So I tried to force having one project directly in one svn - repo. No
progress with release tags. So I retreated back to multi-project svn repo.
Then I found out, that my pom.xml got changed as the maven plugin tried
to increase project version and set up the release. The path to svn repo
(https://....) was changed and contained
<svn_repo_root>/<project_name>/tags/<project_name>-<version>.
So I created folder
<svn_repo_root>/<project_name>/tags
commited it to svn repo and ran
mvn release:rollback release:clean
checked the pom.xml, if there is still SNAPSHOT and no 'tags' in svn
repo path and ran again
mvn release:prepare
The problem with tagging is gone now.
I hope, this helps. I am used to cvs and there was no such problem with
tagging (but the principle of cvs-tagging is kind of magic, compared to
the simple way od svn tags).
Best regards.
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
