[
https://issues.apache.org/jira/browse/SCM-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501853#comment-16501853
]
ASF GitHub Bot commented on SCM-805:
------------------------------------
theit commented on issue #55: Fix for SCM-805
URL: https://github.com/apache/maven-scm/pull/55#issuecomment-394726709
The actual pull request is already based against the master repository.
Concerning your second question: Sure, why not. Testing and verifying this
new feature is certainly good. Although I have to admit that I haven't looked
much into how the tests in `maven-scm-provider-svntest` work...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> 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.10.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
(v7.6.3#76005)
