Hi
This was probably not necessary since there were no code modifications.
Re-run release:perfom would have been enough.
You've forgotten to delete the tag. It's a pity that the codehaus
svn-server doesn't fail if you want to do a svn copy and the tag already
exists.
The result is an extra cobertura-maven-plugin folder within the tag [1]
I suggest to remove the tag and run the release again.
No worries: I think everybody struggles a bit the first time. After a few
releases it's a known process.
Robert
[1] http://svn.codehaus.org/mojo/tags/cobertura-maven-plugin-2.6/
On Sun, 07 Jul 2013 13:22:17 +0200, <schristo...@codehaus.org> wrote:
Revision:
18509
Author:
schristou88
Date:
2013-07-07 06:22:17 -0500 (Sun, 07 Jul 2013)
Log Message
[maven-release-plugin] rollback the release of cobertura-maven-plugin-2.6
Modified Paths
trunk/mojo/cobertura-maven-plugin/pom.xml
Diff
Modified: trunk/mojo/cobertura-maven-plugin/pom.xml (18508 => 18509)
--- trunk/mojo/cobertura-maven-plugin/pom.xml 2013-07-05 14:38:23 UTC
(rev 18508)
+++ trunk/mojo/cobertura-maven-plugin/pom.xml 2013-07-07 11:22:17 UTC
(rev 18509)
@@ -9,7 +9,7 @@
</parent>
<artifactId>cobertura-maven-plugin</artifactId>
- <version>2.7-SNAPSHOT</version>
+ <version>2.6-SNAPSHOT</version>
<packaging>maven-plugin</packaging>
<name>Mojo's Maven plugin for Cobertura</name>
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
