[
https://issues.apache.org/jira/browse/SCM-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962089#comment-17962089
]
ASF GitHub Bot commented on SCM-567:
------------------------------------
jira-importer commented on issue #778:
URL: https://github.com/apache/maven-scm/issues/778#issuecomment-2964623676
**[Olivier
Lamy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=olamy)**
commented
duplicate SCM-623
> Support for git-svn
> -------------------
>
> Key: SCM-567
> URL: https://issues.apache.org/jira/browse/SCM-567
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
> Reporter: Marius Kotsbak
> Assignee: Olivier Lamy
> Priority: Minor
>
> Neither git or svn plugin can be used with release plugin on a svn repository
> checked out using git-svn, so we need probably another
> maven-scm-provider-git-svn or support for that in one of them.
> It will probably need to execute a mix of the two, using "git svn tag" for
> tagging after "git svn dcommit" etc.
> As it is used against a svn repository, it would be best if no configuration
> needs to be changed. Thus either add a command line parameter to enable
> git-svn mode, or better, in plugin for svn, detect that the checkout is done
> using git-svn (the directory .git?), and use that module instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
