[
http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169738#action_169738
]
Olivier Lamy commented on SCM-262:
----------------------------------
After some tests with the release plugin this doesn't work as this (or so
easily)
Story :
- before starting the release your current local rev is 2
- after committing the released pom the svn rev on the server is 3
- but your current local rev is always 2 !
- when we copy : svn cp -r 2 ... .. we copy a non released pom (always
SNAPSHOT version) to the tag path.
We have to get the new svn rev after committing the released pom and use it for
the tag/copy operation.
> 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
> Assignee: Olivier Lamy
> Fix For: 1.2
>
> 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
