Ben Tatham wrote:
Perhaps it is failing the release then, which explains the periodic
nature of "tags" being left in the scm urls. Shouldn't release:clean
supposed to clean this up?
clean will only clean up locally. If you made it half way into a
release, clean will remove all temp files used during the release process.
Or is that what release:rollback is for?
Do you know since what version release:rollback has been available? I
tried it a while back, and even though its documented in the maven site,
it didn't exist yet.
I haven't used rollback myself, but it's my understanding that it rolls
back in the scm as well. The docs says that it's been available since
version 2.0-beta-5.
-Ben
Dennis Lundberg wrote:
Ben Tatham wrote:
Is there a way in the release plugin to have it not change the scm
urls? Or at least put them back as they were on the trunk? I want
the trunk to keep the urls of the trunk, instead of changing it to
tags/project-version everytime. And this change seems to be
inconsistent. Does anyone else see this odd behaviour?
I am using SVN (of course).
-Ben
What the release plugin does is this:
- Change the scm urls in pom.xml on trunk
- Tag the trunk (= svn copy)
- Change the scm urls in pom.xml on trunk back to how they were before
the tagging occured
How is that not working for you? Please supply some configuration and
version info.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
