[
https://issues.apache.org/jira/browse/SCM-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963181#comment-17963181
]
ASF GitHub Bot commented on SCM-805:
------------------------------------
jira-importer commented on issue #1032:
URL: https://github.com/apache/maven-scm/issues/1032#issuecomment-2964640053
**[Thorsten
Heit](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=t_heit)**
commented
[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o),
because the SCM plugin doesn't offer SCM-specific options (at least as far as I
have seen), my first thought was that this is a Subversion-specific feature
that I'd like to configure provider-wide via the provider configuration ([1]).
If you prefer to have this option as specific branch/tag parameters, I can
rework my patch and create a new PR.
> Add SVN --pin-externals option to copy command (branch/tag)
> -----------------------------------------------------------
>
> Key: SCM-805
> URL: https://issues.apache.org/jira/browse/SCM-805
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-svn
> Affects Versions: 1.9.5
> Environment: SVN 1.9+
> Reporter: Eduardo Hernández Guerra
> Assignee: Michael Osipov
> Priority: Major
> Labels: externals, svn, tag
> Fix For: 1.11.1
>
>
> Starting from version 1.9, SVN client now supports the --pin-externals option
> for the copy command, which is to be used when tagging.
> I believe this should be implemented by default in SVN tag operations, and it
> optionally could be disabled via a parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
