You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Torsten Juergeleit (JIRA)" <ji...@codehaus.org> on 2008/11/27 12:59:20 UTC
[jira] Issue Comment Edited: (SCM-406) scm tag does not work with
Subversion 1.5.1
[ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155590#action_155590 ]
Torsten Juergeleit edited comment on SCM-406 at 11/27/08 5:58 AM:
------------------------------------------------------------------
Creating a copy (tag) on a working directory after performing a commit with SVN 1.5.1-1.5.4 seems to be an SVN issue
(please refer to [Error when creating tags from working copy|http://subversion.tigris.org/servlets/BrowseList?list=users&by=thread&from=686753]).
How about implementing the code change (using "cl.createArgument().setValue( repository.getUrl() );" instead of "cl.createArgument().setValue( "." ); ") suggested here by Kyle Lebel or in [SCM-262|http://jira.codehaus.org/browse/SCM-262]?
was (Author: torsten):
Creating a copy (tag) on a working directory after performing a commit with SVN 1.5.1-1.5.4 seems to be an SVN issue
http://subversion.tigris.org/servlets/BrowseList?list=users&by=thread&from=686753
How about implementing the code change (using "cl.createArgument().setValue( repository.getUrl() );" instead of "cl.createArgument().setValue( "." ); ") suggested by Kyle Lebel?
> scm tag does not work with Subversion 1.5.1
> -------------------------------------------
>
> Key: SCM-406
> URL: http://jira.codehaus.org/browse/SCM-406
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.0
> Reporter: James William Dumay
> Fix For: 1.1.1
>
>
> scm:checkin does not work with Subversion 1.5.1
> On release:perform (which I assume calls scm:checkin) the following error occurs:
> {code}
> svn: File '/svn/private/atlassian/confluence/tags/confluence-project-2.10-m1/conf-acceptance-test/pom.xml' already exists
> {code}
> Using subversion 1.4.x is a good enough workaround.
--
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