[
http://jira.codehaus.org/browse/MRELEASE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208822#action_208822
]
werner mueller commented on MRELEASE-514:
-----------------------------------------
a similar issue was solved in MRELEASE-427
since debian 5.0 stable runs with subversion 1.5 this may be around for a while.
> release:branch hit remoteTagging problem
> ----------------------------------------
>
> Key: MRELEASE-514
> URL: http://jira.codehaus.org/browse/MRELEASE-514
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0-beta-9
> Reporter: Benson Margulies
>
> I ran:
> mvn release:branch -DbranchName=rlp_7.1
> and got ...
> {noformat}
> [INFO] Working directory: /Users/benson/x/rex2009-trunk/java
> org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to
> branch SCM
> Provider message:
> The svn branch command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: File '/engineering/rex2009/branches/rlp_7.1/annotatortools/pom.xml'
> already exists
> at
> org.apache.maven.shared.release.phase.ScmBranchPhase.execute(ScmBranchPhase.java:98)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:379)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:350)
> at
> org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:133)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to branch SCM
> Provider message:
> The svn branch command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: File '/engineering/rex2009/branches/rlp_7.1/annotatortools/pom.xml'
> already exists
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
