[
https://issues.apache.org/jira/browse/SCM-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963180#comment-17963180
]
ASF GitHub Bot commented on SCM-805:
------------------------------------
jira-importer commented on issue #1032:
URL: https://github.com/apache/maven-scm/issues/1032#issuecomment-2964640057
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
[Thorsten
Heit](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=t_heit),
there is actually:
http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#remoteTagging
Since we have a very generic API, we cannot satisfy all needs. I think it is
pretty fine to have such specific options: `pinExternals`. In most cases, you
don't need to patch anything if there is no API change. You can simply add a
plugin' dependency
> 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)
