You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Peter Nedonosko <pe...@exoplatform.com.ua> on 2008/11/04 13:59:17 UTC
maven-release-plugin svn branch command failed
Hi guys!
I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
1.5.0_15 and svn 1.5.4.
I cannot run release:branch goal from trunk successful.
Branch commit failed on command
svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
I have tried this command manually
svn copy .
http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
it fails too.
But if I replace '.' on full path of the trunk it will works
svn copy
http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk
http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
I feel it's a bug, but may be I do smth wrong here?
Anybody can help or comment the usecase?
Full error message
[INFO]
------------------------------------------------------------------------
[INFO] Building eXo Kernel
[INFO] task-segment: [release:branch] (aggregator-style)
[INFO]
------------------------------------------------------------------------
[INFO] [release:branch]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive status"
[INFO] Working directory:
D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
What is the new working copy version for "eXo Kernel"?
(org.exoplatform.kernel:config) 2.0.5-SNAPSHOT: :
[INFO] Transforming 'eXo Kernel'...
[INFO] Transforming 'eXo Kernel Commons'...
[INFO] Transforming 'eXo Container'...
[INFO] Updating exo.kernel.commons to 2.0.4-SNAPSHOT
[INFO] Transforming 'Common service'...
[INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
[INFO] Transforming 'Remote service implementation'...
[INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
[INFO] Transforming 'Cache service api'...
[INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
[INFO] Updating exo.kernel.component.remote to 2.0.4-SNAPSHOT
[INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
[INFO] Transforming 'Command service impl'...
[INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
D:\Tmp\maven-scm-142291247.commit --targets D:\Tmp\maven-scm-61108-targets"
[INFO] Working directory:
D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
[INFO] Branching release with the label 2.0.4-RC...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
D:\Tmp\maven-scm-1276451448.commit .
http://svn.exoplatform.org/svnroot/exoplatform/projects/
kernel-new/branches/2.0.4-RC"
[INFO] Working directory:
D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
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
'/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/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:447)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
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:585)
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
'/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml'
already exists
Thanks you,
Peter Nedonosko,
eXo Platform SAS
Re: maven-release-plugin svn branch command failed
Posted by Borut Bolčina <bo...@gmail.com>.
You have to use svn 1.5.0
2008/11/4 Peter Nedonosko <pe...@exoplatform.com.ua>
> Hi guys!
>
> I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
> 1.5.0_15 and svn 1.5.4.
>
Re: maven-release-plugin svn branch command failed
Posted by Arnaud HERITIER <ah...@gmail.com>.
The beta-8 was just released but I didn't notice this bug when I tried it.
You can try the 2.0-beta-7
If it doesn't solve your problem you can try to change you're svn version
like Borut proposes.
If it solves it, you can open an issue ;-)
On Tue, Nov 4, 2008 at 3:11 PM, Peter Nedonosko <
peter.nedonosko@exoplatform.com.ua> wrote:
> Hi,
>
> Thank you for fast feedback!
>
> 2008/11/4 Arnaud HERITIER <ah...@gmail.com>
>
>> Hi Peter,
>>
>> which version of the release plugin are you using? We just released a
>> new version, perhaps there's an issue in it ?
>
>
> I use 2.0-beta-8 version of the plugin.
> Which version do you release?
>
>
>>
>> If you didn't change your version of the plugin it's probably an issue
>> in svn because you are reproducing the issue with the svn command line.
>> There are several problems to create tags with svn 1.5.x. I thought it
>> was fixed, but I'm not sure. There was several threads about this on this
>> mailing list.
>>
>> cheers
>>
>> Arnaud
>>
>>
>> On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko <
>> peter.nedonosko@exoplatform.com.ua> wrote:
>>
>>> Hi guys!
>>>
>>> I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
>>> 1.5.0_15 and svn 1.5.4.
>>>
>>> I cannot run release:branch goal from trunk successful.
>>> Branch commit failed on command
>>> svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
>>>
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>>
>>> I have tried this command manually
>>> svn copy .
>>>
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>> it fails too.
>>>
>>> But if I replace '.' on full path of the trunk it will works
>>> svn copy
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk
>>>
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>>
>>> I feel it's a bug, but may be I do smth wrong here?
>>> Anybody can help or comment the usecase?
>>>
>>>
>>> Full error message
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Building eXo Kernel
>>> [INFO] task-segment: [release:branch] (aggregator-style)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [release:branch]
>>> [INFO] Verifying that there are no local modifications...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive status"
>>> [INFO] Working directory:
>>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>>> What is the new working copy version for "eXo Kernel"?
>>> (org.exoplatform.kernel:config) 2.0.5-SNAPSHOT: :
>>> [INFO] Transforming 'eXo Kernel'...
>>> [INFO] Transforming 'eXo Kernel Commons'...
>>> [INFO] Transforming 'eXo Container'...
>>> [INFO] Updating exo.kernel.commons to 2.0.4-SNAPSHOT
>>> [INFO] Transforming 'Common service'...
>>> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
>>> [INFO] Transforming 'Remote service implementation'...
>>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>>> [INFO] Transforming 'Cache service api'...
>>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>>> [INFO] Updating exo.kernel.component.remote to 2.0.4-SNAPSHOT
>>> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
>>> [INFO] Transforming 'Command service impl'...
>>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>>> [INFO] Checking in modified POMs...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
>>> D:\Tmp\maven-scm-142291247.commit --targets
>>> D:\Tmp\maven-scm-61108-targets"
>>> [INFO] Working directory:
>>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>>> [INFO] Branching release with the label 2.0.4-RC...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
>>> D:\Tmp\maven-scm-1276451448.commit .
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/
>>> kernel-new/branches/2.0.4-RC<http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC>
>>> "
>>> [INFO] Working directory:
>>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>>> 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
>>>
>>> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/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:447)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>>> 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:585)
>>> 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
>>>
>>> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml'
>>> already exists
>>>
>>>
>>>
>>> Thanks you,
>>>
>>> Peter Nedonosko,
>>> eXo Platform SAS
>>>
>>
>>
>>
>> --
>> ..........................................................
>> Arnaud HERITIER
>> ..........................................................
>> OCTO Technology - aheritier AT octo DOT com
>> www.octo.com | blog.octo.com
>> ..........................................................
>> ASF - aheritier AT apache DOT org
>> www.apache.org | maven.apache.org
>> ...........................................................
>>
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
Re: maven-release-plugin svn branch command failed
Posted by Arnaud HERITIER <ah...@gmail.com>.
The beta-8 was just released but I didn't notice this bug when I tried it.
You can try the 2.0-beta-7
If it doesn't solve your problem you can try to change you're svn version
like Borut proposes.
If it solves it, you can open an issue ;-)
On Tue, Nov 4, 2008 at 3:11 PM, Peter Nedonosko <
peter.nedonosko@exoplatform.com.ua> wrote:
> Hi,
>
> Thank you for fast feedback!
>
> 2008/11/4 Arnaud HERITIER <ah...@gmail.com>
>
>> Hi Peter,
>>
>> which version of the release plugin are you using? We just released a
>> new version, perhaps there's an issue in it ?
>
>
> I use 2.0-beta-8 version of the plugin.
> Which version do you release?
>
>
>>
>> If you didn't change your version of the plugin it's probably an issue
>> in svn because you are reproducing the issue with the svn command line.
>> There are several problems to create tags with svn 1.5.x. I thought it
>> was fixed, but I'm not sure. There was several threads about this on this
>> mailing list.
>>
>> cheers
>>
>> Arnaud
>>
>>
>> On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko <
>> peter.nedonosko@exoplatform.com.ua> wrote:
>>
>>> Hi guys!
>>>
>>> I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
>>> 1.5.0_15 and svn 1.5.4.
>>>
>>> I cannot run release:branch goal from trunk successful.
>>> Branch commit failed on command
>>> svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
>>>
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>>
>>> I have tried this command manually
>>> svn copy .
>>>
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>> it fails too.
>>>
>>> But if I replace '.' on full path of the trunk it will works
>>> svn copy
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk
>>>
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>>
>>> I feel it's a bug, but may be I do smth wrong here?
>>> Anybody can help or comment the usecase?
>>>
>>>
>>> Full error message
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Building eXo Kernel
>>> [INFO] task-segment: [release:branch] (aggregator-style)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [release:branch]
>>> [INFO] Verifying that there are no local modifications...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive status"
>>> [INFO] Working directory:
>>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>>> What is the new working copy version for "eXo Kernel"?
>>> (org.exoplatform.kernel:config) 2.0.5-SNAPSHOT: :
>>> [INFO] Transforming 'eXo Kernel'...
>>> [INFO] Transforming 'eXo Kernel Commons'...
>>> [INFO] Transforming 'eXo Container'...
>>> [INFO] Updating exo.kernel.commons to 2.0.4-SNAPSHOT
>>> [INFO] Transforming 'Common service'...
>>> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
>>> [INFO] Transforming 'Remote service implementation'...
>>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>>> [INFO] Transforming 'Cache service api'...
>>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>>> [INFO] Updating exo.kernel.component.remote to 2.0.4-SNAPSHOT
>>> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
>>> [INFO] Transforming 'Command service impl'...
>>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>>> [INFO] Checking in modified POMs...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
>>> D:\Tmp\maven-scm-142291247.commit --targets
>>> D:\Tmp\maven-scm-61108-targets"
>>> [INFO] Working directory:
>>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>>> [INFO] Branching release with the label 2.0.4-RC...
>>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
>>> D:\Tmp\maven-scm-1276451448.commit .
>>> http://svn.exoplatform.org/svnroot/exoplatform/projects/
>>> kernel-new/branches/2.0.4-RC<http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC>
>>> "
>>> [INFO] Working directory:
>>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>>> 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
>>>
>>> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/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:447)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
>>> at
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>>> 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:585)
>>> 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
>>>
>>> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml'
>>> already exists
>>>
>>>
>>>
>>> Thanks you,
>>>
>>> Peter Nedonosko,
>>> eXo Platform SAS
>>>
>>
>>
>>
>> --
>> ..........................................................
>> Arnaud HERITIER
>> ..........................................................
>> OCTO Technology - aheritier AT octo DOT com
>> www.octo.com | blog.octo.com
>> ..........................................................
>> ASF - aheritier AT apache DOT org
>> www.apache.org | maven.apache.org
>> ...........................................................
>>
>
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
Re: maven-release-plugin svn branch command failed
Posted by Peter Nedonosko <pe...@exoplatform.com.ua>.
Hi,
Thank you for fast feedback!
2008/11/4 Arnaud HERITIER <ah...@gmail.com>
> Hi Peter,
>
> which version of the release plugin are you using? We just released a new
> version, perhaps there's an issue in it ?
I use 2.0-beta-8 version of the plugin.
Which version do you release?
>
> If you didn't change your version of the plugin it's probably an issue in
> svn because you are reproducing the issue with the svn command line.
> There are several problems to create tags with svn 1.5.x. I thought it
> was fixed, but I'm not sure. There was several threads about this on this
> mailing list.
>
> cheers
>
> Arnaud
>
>
> On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko <
> peter.nedonosko@exoplatform.com.ua> wrote:
>
>> Hi guys!
>>
>> I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
>> 1.5.0_15 and svn 1.5.4.
>>
>> I cannot run release:branch goal from trunk successful.
>> Branch commit failed on command
>> svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
>>
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>
>> I have tried this command manually
>> svn copy .
>>
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>> it fails too.
>>
>> But if I replace '.' on full path of the trunk it will works
>> svn copy
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk
>>
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>
>> I feel it's a bug, but may be I do smth wrong here?
>> Anybody can help or comment the usecase?
>>
>>
>> Full error message
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building eXo Kernel
>> [INFO] task-segment: [release:branch] (aggregator-style)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [release:branch]
>> [INFO] Verifying that there are no local modifications...
>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive status"
>> [INFO] Working directory:
>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>> What is the new working copy version for "eXo Kernel"?
>> (org.exoplatform.kernel:config) 2.0.5-SNAPSHOT: :
>> [INFO] Transforming 'eXo Kernel'...
>> [INFO] Transforming 'eXo Kernel Commons'...
>> [INFO] Transforming 'eXo Container'...
>> [INFO] Updating exo.kernel.commons to 2.0.4-SNAPSHOT
>> [INFO] Transforming 'Common service'...
>> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
>> [INFO] Transforming 'Remote service implementation'...
>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>> [INFO] Transforming 'Cache service api'...
>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>> [INFO] Updating exo.kernel.component.remote to 2.0.4-SNAPSHOT
>> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
>> [INFO] Transforming 'Command service impl'...
>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
>> D:\Tmp\maven-scm-142291247.commit --targets
>> D:\Tmp\maven-scm-61108-targets"
>> [INFO] Working directory:
>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>> [INFO] Branching release with the label 2.0.4-RC...
>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
>> D:\Tmp\maven-scm-1276451448.commit .
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/
>> kernel-new/branches/2.0.4-RC<http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC>
>> "
>> [INFO] Working directory:
>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>> 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
>>
>> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/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:447)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>> 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:585)
>> 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
>>
>> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml'
>> already exists
>>
>>
>>
>> Thanks you,
>>
>> Peter Nedonosko,
>> eXo Platform SAS
>>
>
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
Re: maven-release-plugin svn branch command failed
Posted by Peter Nedonosko <pe...@exoplatform.com.ua>.
Hi,
Thank you for fast feedback!
2008/11/4 Arnaud HERITIER <ah...@gmail.com>
> Hi Peter,
>
> which version of the release plugin are you using? We just released a new
> version, perhaps there's an issue in it ?
I use 2.0-beta-8 version of the plugin.
Which version do you release?
>
> If you didn't change your version of the plugin it's probably an issue in
> svn because you are reproducing the issue with the svn command line.
> There are several problems to create tags with svn 1.5.x. I thought it
> was fixed, but I'm not sure. There was several threads about this on this
> mailing list.
>
> cheers
>
> Arnaud
>
>
> On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko <
> peter.nedonosko@exoplatform.com.ua> wrote:
>
>> Hi guys!
>>
>> I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
>> 1.5.0_15 and svn 1.5.4.
>>
>> I cannot run release:branch goal from trunk successful.
>> Branch commit failed on command
>> svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
>>
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>
>> I have tried this command manually
>> svn copy .
>>
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>> it fails too.
>>
>> But if I replace '.' on full path of the trunk it will works
>> svn copy
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk
>>
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>>
>> I feel it's a bug, but may be I do smth wrong here?
>> Anybody can help or comment the usecase?
>>
>>
>> Full error message
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building eXo Kernel
>> [INFO] task-segment: [release:branch] (aggregator-style)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [release:branch]
>> [INFO] Verifying that there are no local modifications...
>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive status"
>> [INFO] Working directory:
>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>> What is the new working copy version for "eXo Kernel"?
>> (org.exoplatform.kernel:config) 2.0.5-SNAPSHOT: :
>> [INFO] Transforming 'eXo Kernel'...
>> [INFO] Transforming 'eXo Kernel Commons'...
>> [INFO] Transforming 'eXo Container'...
>> [INFO] Updating exo.kernel.commons to 2.0.4-SNAPSHOT
>> [INFO] Transforming 'Common service'...
>> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
>> [INFO] Transforming 'Remote service implementation'...
>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>> [INFO] Transforming 'Cache service api'...
>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>> [INFO] Updating exo.kernel.component.remote to 2.0.4-SNAPSHOT
>> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
>> [INFO] Transforming 'Command service impl'...
>> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
>> D:\Tmp\maven-scm-142291247.commit --targets
>> D:\Tmp\maven-scm-61108-targets"
>> [INFO] Working directory:
>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>> [INFO] Branching release with the label 2.0.4-RC...
>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
>> D:\Tmp\maven-scm-1276451448.commit .
>> http://svn.exoplatform.org/svnroot/exoplatform/projects/
>> kernel-new/branches/2.0.4-RC<http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC>
>> "
>> [INFO] Working directory:
>> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
>> 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
>>
>> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/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:447)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
>> at
>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>> 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:585)
>> 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
>>
>> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml'
>> already exists
>>
>>
>>
>> Thanks you,
>>
>> Peter Nedonosko,
>> eXo Platform SAS
>>
>
>
>
> --
> ..........................................................
> Arnaud HERITIER
> ..........................................................
> OCTO Technology - aheritier AT octo DOT com
> www.octo.com | blog.octo.com
> ..........................................................
> ASF - aheritier AT apache DOT org
> www.apache.org | maven.apache.org
> ...........................................................
>
Re: maven-release-plugin svn branch command failed
Posted by Arnaud HERITIER <ah...@gmail.com>.
Hi Peter,
which version of the release plugin are you using? We just released a new
version, perhaps there's an issue in it ?
If you didn't change your version of the plugin it's probably an issue in
svn because you are reproducing the issue with the svn command line.
There are several problems to create tags with svn 1.5.x. I thought it was
fixed, but I'm not sure. There was several threads about this on this
mailing list.
cheers
Arnaud
On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko <
peter.nedonosko@exoplatform.com.ua> wrote:
> Hi guys!
>
> I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
> 1.5.0_15 and svn 1.5.4.
>
> I cannot run release:branch goal from trunk successful.
> Branch commit failed on command
> svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
>
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>
> I have tried this command manually
> svn copy .
>
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
> it fails too.
>
> But if I replace '.' on full path of the trunk it will works
> svn copy
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk
>
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>
> I feel it's a bug, but may be I do smth wrong here?
> Anybody can help or comment the usecase?
>
>
> Full error message
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building eXo Kernel
> [INFO] task-segment: [release:branch] (aggregator-style)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [release:branch]
> [INFO] Verifying that there are no local modifications...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive status"
> [INFO] Working directory:
> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
> What is the new working copy version for "eXo Kernel"?
> (org.exoplatform.kernel:config) 2.0.5-SNAPSHOT: :
> [INFO] Transforming 'eXo Kernel'...
> [INFO] Transforming 'eXo Kernel Commons'...
> [INFO] Transforming 'eXo Container'...
> [INFO] Updating exo.kernel.commons to 2.0.4-SNAPSHOT
> [INFO] Transforming 'Common service'...
> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
> [INFO] Transforming 'Remote service implementation'...
> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
> [INFO] Transforming 'Cache service api'...
> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
> [INFO] Updating exo.kernel.component.remote to 2.0.4-SNAPSHOT
> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
> [INFO] Transforming 'Command service impl'...
> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
> D:\Tmp\maven-scm-142291247.commit --targets D:\Tmp\maven-scm-61108-targets"
> [INFO] Working directory:
> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
> [INFO] Branching release with the label 2.0.4-RC...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
> D:\Tmp\maven-scm-1276451448.commit .
> http://svn.exoplatform.org/svnroot/exoplatform/projects/
> kernel-new/branches/2.0.4-RC<http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC>
> "
> [INFO] Working directory:
> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
> 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
>
> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/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:447)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> 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:585)
> 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
>
> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml'
> already exists
>
>
>
> Thanks you,
>
> Peter Nedonosko,
> eXo Platform SAS
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
Re: maven-release-plugin svn branch command failed
Posted by John Stoneham <ly...@lyrically.net>.
tespackman wrote:
> I've run into the same problem, but somehow I managed to figure it out!!
>
> I found that if I simply run an "svn up" right before executing the mvn
> release:branch command it works!
>
> Note that there are NO changes downloaded from the scm, but for whatever
> reason it worked for me.
This is a known issue with the release plugin and Subversion 1.5.1+.
You'll run into the same issue on a release:prepare. The problem has to
do with the fact that the release plugin checks into a new branch (or
tag) directly from the working copy, rather than committing and copying
first. (Reason has to do with making sure nothing committed on the trunk
while the preparation goals are running gets into the tag.) This worked
fine up through SVN 1.5.0.
Googling on the error message you get (something about "xyz already
exists") should get you some additional details. Best known workaround I
have for now is to downgrade to SVN 1.5.0; last I heard this is still an
issue with maven-release-plugin 2.0-beta-8 and SVN 1.5.4.
- John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-release-plugin svn branch command failed
Posted by tespackman <te...@yahoo.com>.
I've run into the same problem, but somehow I managed to figure it out!!
I found that if I simply run an "svn up" right before executing the mvn
release:branch command it works!
Note that there are NO changes downloaded from the scm, but for whatever
reason it worked for me.
Peter Nedonosko wrote:
>
> Hi guys!
>
> I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
> 1.5.0_15 and svn 1.5.4.
>
> I cannot run release:branch goal from trunk successful.
> Branch commit failed on command
> svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>
> I have tried this command manually
> svn copy .
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
> it fails too.
>
> But if I replace '.' on full path of the trunk it will works
> svn copy
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>
> I feel it's a bug, but may be I do smth wrong here?
> Anybody can help or comment the usecase?
>
>
--
View this message in context: http://www.nabble.com/maven-release-plugin-svn-branch-command-failed-tp20321804p20629606.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-release-plugin svn branch command failed
Posted by Arnaud HERITIER <ah...@gmail.com>.
Hi Peter,
which version of the release plugin are you using? We just released a new
version, perhaps there's an issue in it ?
If you didn't change your version of the plugin it's probably an issue in
svn because you are reproducing the issue with the svn command line.
There are several problems to create tags with svn 1.5.x. I thought it was
fixed, but I'm not sure. There was several threads about this on this
mailing list.
cheers
Arnaud
On Tue, Nov 4, 2008 at 1:59 PM, Peter Nedonosko <
peter.nedonosko@exoplatform.com.ua> wrote:
> Hi guys!
>
> I try to use maven-release-plugin on WindowsXP SP2 with maven 2.0.8, Java
> 1.5.0_15 and svn 1.5.4.
>
> I cannot run release:branch goal from trunk successful.
> Branch commit failed on command
> svn --non-interactive copy --file D:\Tmp\maven-scm-1276451448.commit .
>
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>
> I have tried this command manually
> svn copy .
>
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
> it fails too.
>
> But if I replace '.' on full path of the trunk it will works
> svn copy
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/trunk
>
> http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC
>
> I feel it's a bug, but may be I do smth wrong here?
> Anybody can help or comment the usecase?
>
>
> Full error message
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building eXo Kernel
> [INFO] task-segment: [release:branch] (aggregator-style)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [release:branch]
> [INFO] Verifying that there are no local modifications...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive status"
> [INFO] Working directory:
> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
> What is the new working copy version for "eXo Kernel"?
> (org.exoplatform.kernel:config) 2.0.5-SNAPSHOT: :
> [INFO] Transforming 'eXo Kernel'...
> [INFO] Transforming 'eXo Kernel Commons'...
> [INFO] Transforming 'eXo Container'...
> [INFO] Updating exo.kernel.commons to 2.0.4-SNAPSHOT
> [INFO] Transforming 'Common service'...
> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
> [INFO] Transforming 'Remote service implementation'...
> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
> [INFO] Transforming 'Cache service api'...
> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
> [INFO] Updating exo.kernel.component.remote to 2.0.4-SNAPSHOT
> [INFO] Updating exo.kernel.container to 2.0.4-SNAPSHOT
> [INFO] Transforming 'Command service impl'...
> [INFO] Updating exo.kernel.component.common to 2.0.4-SNAPSHOT
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive commit --file
> D:\Tmp\maven-scm-142291247.commit --targets D:\Tmp\maven-scm-61108-targets"
> [INFO] Working directory:
> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
> [INFO] Branching release with the label 2.0.4-RC...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file
> D:\Tmp\maven-scm-1276451448.commit .
> http://svn.exoplatform.org/svnroot/exoplatform/projects/
> kernel-new/branches/2.0.4-RC<http://svn.exoplatform.org/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC>
> "
> [INFO] Working directory:
> D:\Projects\eXo\dev\projects\projects-lab\kernel-new\trunk
> 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
>
> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/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:447)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> 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:585)
> 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
>
> '/svnroot/exoplatform/projects/kernel-new/branches/2.0.4-RC/commons/pom.xml'
> already exists
>
>
>
> Thanks you,
>
> Peter Nedonosko,
> eXo Platform SAS
>
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................