this morning i upgraded from subversion 1.5.0 to 1.5.1 via macports.
this afternoon, i tried to do a release of some software at work.. and the maven release plugin was failing! its a very odd error:
[INFO] Tagging release with the label release-0.4...
[INFO] Executing: svn --non-interactive copy --file /tmp/maven-scm-1130425261.commit . https://example.com/workstuff/release-0.4
[INFO] Working directory: /Users/osi/Documents/workstuff/trunk
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: File '/workstuff/tags/release-0.4/pom.xml' already exists
very weird. i tried executing that same command at the prompt, and got the same error. i did a svn up, and then it worked.. hrm. thankfully, macports makes it very easy to drop back to 1.5.0, and after i did that, maven was able to release no problem.
UPDATE: using 2.0-beta-9 of the maven-release-plugin has a workaround for this issue.
Tags: development, maven
September 5th, 2008 at 2:28 pm
I am getting this error, also. Actually with one of my projects repeating the command worked. On another project … I repeated the command 10 times, it failed 9 out of 10 times with that error. Then it worked, but failed for a different reason (my fault). Now I can’t get it to release again after another 10 times.
Just posting this so any other very frustrated developer looking for this problem won’t think they’re insane.
October 6th, 2008 at 10:04 am
I got this error too!!! That sounds horrible, just an update and it works… thank you for the hint, this problem was driving me crazy!
October 14th, 2008 at 5:47 am
Verified this error on both SVN 1.5.1 and after upgrading to 1.5.3 as well. Does anyone know if this is a maven or svn bug – did maven-release-plugin perhaps depend on a feature-bug?
February 18th, 2009 at 1:17 pm
On http://nachtfrost.wordpress.com/2009/02/12/maven-release-plugin-und-subversion-15x/ I found this workaround:
When the mvn release:prepare step fails, do svn up and then do mvn release:prepare again – and it works like a charm
March 5th, 2009 at 8:19 am
I hope this error will be fixed soon – seems like they are not sure if it is a Maven or Subversion bug (see http://jira.codehaus.org/browse/SCM-406)
March 28th, 2009 at 5:50 pm
Hi there!
I had the same issue, it’s a change in subversion’s tagging behavior and new scm plugin versions will fix it, in the meantime there is an easy, safe & clean workaround described in the issues. I’ve documented the necessary changes here:
http://olafsblog.sysbsb.de/?p=73
best,
Olaf