maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (JIRA)" <>
Subject [jira] Commented: (MRELEASE-514) release:branch hit remoteTagging problem
Date Mon, 01 Feb 2010 00:18:55 GMT


Stephen Connolly commented on MRELEASE-514:

Did you have a mixed revision working copy?

I have seen this type of issue just creating tags using svn directly.

If you modify files locally, commit just those files and then do an svn cp without doing an
svn update first, then you can end up with the above issue.

If this is a case of a mixed revision working copy, then there may not be an easy way to fix
this, we could force an svn update, but that might be counter to what the user is trying to
do, e.g. they may want to branch from their working copy... which has some files updated to
HEAD while others have not been updated (because the update would break the code)

> release:branch hit remoteTagging problem
> ----------------------------------------
>                 Key: MRELEASE-514
>                 URL:
>             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(
> 	at org.apache.maven.shared.release.DefaultReleaseManager.branch(
> 	at org.apache.maven.shared.release.DefaultReleaseManager.branch(
> 	at org.apache.maven.plugins.release.BranchReleaseMojo.execute(
> 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> 	at org.apache.maven.DefaultMaven.doExecute(
> 	at org.apache.maven.DefaultMaven.execute(
> 	at org.apache.maven.cli.MavenCli.main(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.codehaus.classworlds.Launcher.launchEnhanced(
> 	at org.codehaus.classworlds.Launcher.launch(
> 	at org.codehaus.classworlds.Launcher.mainWithExitCode(
> 	at org.codehaus.classworlds.Launcher.main(
> [INFO] ------------------------------------------------------------------------
> [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:
For more information on JIRA, see:


View raw message