[ 
https://issues.apache.org/jira/browse/SCM-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964248#comment-17964248
 ] 

Olivier Lamy commented on SCM-68:
---------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-scm#325|https://github.com/apache/maven-scm/issues/325]. 

> Subversion provider doesn't handle tag updates correctly
> --------------------------------------------------------
>
>                 Key: SCM-68
>                 URL: https://issues.apache.org/jira/browse/SCM-68
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.0-alpha-4
>            Reporter: David Hawkins
>            Assignee: Emmanuel Venisse
>            Priority: Major
>             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 was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to