[
http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167661#action_167661
]
Karsten Sperling commented on SCM-262:
--------------------------------------
Tagging from a fixed revision is only equivalent to tagging from a working copy
if the working copy is at a consistent revision across all files, i.e. only if
'svn info -R | grep Revision' shows the same revision number for all files.
Maven should enforce this at the same time as it checks for local modifications.
In fact, to be completely correct, maven would have to be even more paranoid
during release:prepare
- Check that svn st -u shows neither local nor remote changes. The output will
also contain the latest revision for the tree on the server, call it R1
- svn up -r $R1. This should not result in any changes
- Commit the POM update, call the revision this results in R2
- Check that no intervening changes were committed on the server: svn log -q -r
$R1:$R2. This should only return the two revisions R1 and R2, but nothing in
between
- Making a tag of R2 will now have the same content as the original working
copy (+ POM change)
> 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
