[
https://issues.apache.org/jira/browse/SCM-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960294#comment-17960294
]
ASF GitHub Bot commented on SCM-72:
-----------------------------------
jira-importer commented on issue #372:
URL: https://github.com/apache/maven-scm/issues/372#issuecomment-2964590165
**[Emmanuel
Venisse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evenisse)**
commented
After a discussion with David, we won't remove tagbase. We'll use it if it's
specified but by default, we'll consider that user use a standard repository
layout (trunk/, tags/, branches)
If user use a standard layout, tags directory is automatically discover.
And the other feature added in update command is the support of standard svn
revision specifiers (HEAD, BASE, COMMITTED, PREV) and revision number
The last feature is if tag != null or it isn't a revision number, we use the
svn switch command instead of update
> Remove tagbase usage and use insted mecanism use in update command
> ------------------------------------------------------------------
>
> Key: SCM-72
> URL: https://issues.apache.org/jira/browse/SCM-72
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: maven-scm-provider-svn
> Affects Versions: 1.0-beta-1
> Reporter: Emmanuel Venisse
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-beta-1
>
> Attachments: SCM-72-maven-scm-test.patch,
> SCM-72-maven.scm-provider-svn.patch
>
>
> David Hawkins, do you want work on it?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
