I had a similar failure when doing the classpool release, but it was not
same error as you (can't tag it cause the message was repository does
not exist).
This is what I've done:
- I checked that I forgot to define my username and password
- During the first release try, the pom was updated and for some strange
reason, I got an error and the scm address moved from trunk to tag
(don't ask me why). I had to fix my pom then.
- downgraded the version of release plugin to 2.0-beta-8
Downgrading didn't work for me as the other two points were the cause of
the problem. But I found an e-mail thread on the web that mentioned that
2.0-beta-9 has a bug and that causes maven to not be able to tag it.
That's why I gave it a try. Maybe this will solve your problem?
On 12/19/2009 04:54 PM, Ales Justin wrote:
Any idea what might be wrong?
Or is this just one of those "mvn release:x" random failures?
---------------------------------------------------------------------
[INFO] Tagging release with the label 1.0.0.Alpha1...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
C:\DOCUME~1\Ales\LOCALS~1\Temp\maven-scm-578495977.commit --revision
98027
https://svn.jboss.org/repos/labs/labs/jbossbuild/jboss-parent/tags/jboss-...
https://svn.jboss.org/repos/jbossas/projects/mc-ann/tags/1.0.0.Alpha1"
[INFO] Working directory: C:\projects\microcontainer\mc-ann
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Repository moved permanently to 'https://svn.jboss.org/repos/';
please relocate
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Flavia Rainone | JBoss Core Developer
M: (+55) (+11) 8122-5466
YIM/MSNIM: flaviarnn