[
https://issues.apache.org/jira/browse/SCM-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963179#comment-17963179
]
ASF GitHub Bot commented on SCM-805:
------------------------------------
jira-importer commented on issue #1032:
URL: https://github.com/apache/maven-scm/issues/1032#issuecomment-2964640055
**[Thorsten
Heit](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=t_heit)**
commented
I forgot:
Another reason why I added this to the `svn-settings.xml` was that I haven't
found out a clear way to make it work with the maven-release-plugin (2.5.3) :
m-release-p uses a hard-coded version 1.9.5 of m-scm-p as far as I know so I
had to patch this plugin too to use my own m-scm-p variant. Without this I'm
not able to perform a release with Maven via "mvn release:prepare
release:perform" so that svn externals are pinned.
In case that svn externals pinning is realized via `ScmBranchParameters` and
`ScmTagParameters`, m-release-p has to be patched a bit more apart from using a
newer m-scm-p version:
It creates new instances of these objects in `ScmBranchPhase.java` and
`ScmTagPhase.java` when branching and/or tagging is being performed.
> 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)
