I had exactly the same error when I tried to release the tranql oracle wrapper at codehaus a few days ago. After trying a lot of things unsuccessfully I ended up

1. running release:prepare (it updates svn with the new version and tries to copy the working copy into the svn tag, which fails) 2. manually copying the svn trunk/branch to tags (the maven output includes the svn command that fails, basically svn cp . https/foo/tags/ tag-name, I changed it to svn cp https://foo/trunk https/foo/tags/tag- name) 3. updating the local properties file that indicates how far the release plugin got to claim it successfully did the copy 4. running mvn release:prepare again (now it succeeds since it thinks _it_ did the copy)
5. running mvn release:perform.

I'm not sure its a maven problem because running the svn command maven tries also fails from the command line. So I wonder if its an svn bug????

thanks
david jencks

On Mar 9, 2009, at 1:15 AM, David Blevins wrote:

Running into issues here. Hopefully one of the maven guys can help tomorrow.

The release:prepare phase keeps failing with:
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: File '/repos/asf/openejb/tags/openejb-3.0.1/assembly/openejb- itests-standalone-client/pom.xml' already exists

I tried to tag manually from that same checkout and got the same error. I had to grab a new checkout and then I was finally able to tag. Didn't seem to matter as the release:perform refuses to do anything since I went off-book.

-David

On Mar 6, 2009, at 4:20 PM, David Blevins wrote:

FYI, got the poms updated for the nexus stuff. Still running into some issues. Working with Brain Fox to get them resolved. Hopefully I'll have some jars up in the staging repo for a vote soon.

-David

On Mar 4, 2009, at 10:41 AM, Joe Bohn wrote:

David,

The latest 3.0.1-SNAPSHOT looks good to us (Geronimo) on all levels. Can we get a release of this soon?

Thanks for all your help!
Joe


David Blevins wrote:
As an FYI for those that don't track Geronimo development. Geronimo is releasing a 2.1.4 and needs a fix from the OpenEJB 3.0.x stream. Going to create a branch from our 3.0 tag, update it to 3.0.1-SNAPSHOT and start applying the required fixes.
-David






Reply via email to