I get that error all too often, as well. I haven't found a solution for it.
On Sat, Sep 4, 2010 at 3:35 PM, Dennis Lundberg wrote:
> On 2010-09-04 00:16, Neil Chaudhuri wrote:
>> I am using version 2.0 of the release plugin to tag a new version of my
>> multi-module application, but at the end when it goes to commit to SVN SCM,
>> I get the following:
>>
>> [INFO] Unable to tag SCM
>> Provider message:
>> The svn tag command failed.
>> Command output:
>> svn: Path 'svn:///data/svn/client/myapp/tags/myapp-1.1.rc4' does not
>> exist in revision 5218
>>
>> To be fair, that's true--myapp-1.1.rc4 isn't a folder in the SVN tags
>> folder. But I figured the plugin would create it and put my source code
>> underneath.
>>
>> Another weird thing is that the poms are updated to 1.1.rc4 and committed to
>> the trunk and checked out to my local machine. The expected behavior is for
>> 1.1.rc5-SNAPSHOT to be in the trunk and on my local while the 1.1.rc4 is in
>> the tagged version.
>>
>> Here is the plugin configuration:
>>
>>
>> org.apache.maven.plugins
>> maven-release-plugin
>> 2.0
>>
>>
>> false
>> clean install
>> clean install
>> -Dmaven.test.skip
>> svn:///data/svn/client/myapp/tags
>>
>> true
>>
>>
>>
>> Any advice on how to get the expected behavior is appreciated.
>
> is only available in the branch goal. Are
> you trying to release from a branch?
>
> If so then by using updateWorkingCopyVersions=false you have told the
> plugin that you don't want it to update the version in your working copy.
>
>>
>> Thanks.
>>
>
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
