[
http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Rudd updated SCM-262:
---------------------------
Attachment: SvnTagCommand.patch
Here is a patch that I made against version 1.0. It uses the svn info command
on the working directory to get the current revision (presumably the revision
that was built) and passes the revision to the svn cp command. This works with
svn 1.5.4 (have not tested other versions, but dont see any reason it wouldnt).
> 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
>
> Attachments: SvnTagCommand.patch
>
>
> 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
