[
https://issues.apache.org/jira/browse/SCM-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960295#comment-17960295
]
ASF GitHub Bot commented on SCM-72:
-----------------------------------
jira-importer commented on issue #372:
URL: https://github.com/apache/maven-scm/issues/372#issuecomment-2964590161
**[John Dennis
Casey](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jdcasey)**
commented
what's the mechanism used in the update command? What changes are necessary
for the release mojo to support this new approach?
> 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)
