You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-dev@maven.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2005/11/10 22:29:06 UTC
[jira] Closed: (SCM-68) Subversion provider doesn't handle tag updates correctly
[ http://jira.codehaus.org/browse/SCM-68?page=all ]
Emmanuel Venisse closed SCM-68:
-------------------------------
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0-beta-1
Applied, thanks
> Subversion provider doesn't handle tag updates correctly
> --------------------------------------------------------
>
> Key: SCM-68
> URL: http://jira.codehaus.org/browse/SCM-68
> Project: Maven SCM
> Type: Bug
> Components: maven-scm-provider-svn
> Versions: 1.0-alpha-4
> Reporter: David Hawkins
> Assignee: Emmanuel Venisse
> Fix For: 1.0-beta-1
> Attachments: update-switch-revised.patch, update-switch.patch
>
>
> When attempting to use Continuum I kept having problems where Continuum would checkout the project fine, but always fail to update it on subsequent builds. Continuum forces you to specify a scmTagBase as well as a scmTag for subversion projects. The problem is that is passes the tag to the scm update which ends up issuing a svn command with -r tagname
> Example:
> checkout command:
> svn --non-interactive checkout http://svn/projects/dmi-jdbc/branches/my-branch-name 6
> update command
> svn --non-interactive update -r branches/my-branch-name
> This probably works fine in cvs because a tag can refer to a revision or tag. In subversion, tags and revisions are obviously very different so the SvnUpdateCommand should handle the two cases differently if you are requesting a revision or an actual tag.
> I've created a patch which corrects the problem and causes SvnUpdateCommand to perform a switch to update whenever a non revision tag is specified. I believe this will produce the intended results, but I am also fairly new to subversion and its possible it doesn't.
> Please let me know if you need more information.
> --David
--
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