[jira] Commented: (SCM-262) scm:tag for subversion tagging from local version of code, not directly from repository

["Chris Rudd (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163763#action_163763 ] 

Chris Rudd commented on SCM-262:
--------------------------------

The svn command that fails is :

svn copy --file /tmp/maven-scm-297444897.commit . http://XXX/svn/project/tags/foo-1.0.0

Simply adding the explicit revision to copy from solves the problem 

svn copy --file /tmp/maven-scm-297444897.commit -r 599 . http://XXX/svn/project/tags/foo-1.0.0

So is there an easy way for the SvnTagCommand to get the revision of the local copy?


> scm:tag for subversion tagging from local version of code, not directly from repository
> ---------------------------------------------------------------------------------------
>
>                 Key: SCM-262
>                 URL: http://jira.codehaus.org/browse/SCM-262
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>            Reporter: Stephan Heilner
>             Fix For: future
>
>
> In theory, you shouldn't tag or branch from a local and potentially different version of the code.  From what I can tell, the scm:tag imports your existing code into a new tag.  With subversion, tagging is very lightweight if you do a 'svn copy trunk_url tag_url'.  The way it currently works make sense for other repositories such as CVS but not for subversion.  

-- 
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