[SCM-68] Subversion provider doesn't handle tag updates correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0-alpha-4
• Fix Version/s: 1.0-beta-1
• Component/s: maven-scm-provider-svn
• Assignee: Emmanuel Venisse
• Reporter: David Hawkins
• Created: 05/Nov/05 21:25
• Updated: 13/Mar/06 04:08
• Resolved: 10/Nov/05 15:28

Description

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