[ https://issues.apache.org/jira/browse/SCM-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759132#comment-16759132 ] 

Michael Osipov edited comment on SCM-917 at 2/2/19 7:46 PM:
------------------------------------------------------------

I pretty much do not care how the SCM implements the usecase. Maven SCM tries to be system-agnostic. Subversion does not have the concept of branches and tags. Therefore {{scm:tag}} and {{scm:untag}} will use the semantics of the SCM, here in Subversion {{cp}} and {{rm}}.


was (Author: michael-o):
I pretty much do not care how the SCM implements the usecase. SCM tries to be system-agnostic. Subversion does not have the concept of branches and tags. Therefore {{scm:tag}} and {{scm:untag}} will use the semantics of the SCM, here in Subversion {{cp}} and {{rm}}.

> Enable remote scm:remove
> ------------------------
>
>                 Key: SCM-917
>                 URL: https://issues.apache.org/jira/browse/SCM-917
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.11.1
>            Reporter: Clemens Quoß
>            Priority: Critical
>             Fix For: waiting-for-feedback
>
>         Attachments: image-2019-02-02-16-57-33-664.png
>
>
> In order to work on MRELEASE-229, I would like to provide a PR for SCM to enable remote removal for provider svn.
> Short outline:
> Introducing new parameter on scm:remove "remoteRemove" (alternative: use pushChanges for this for svn, but this might be confusing).
> Implementation:
> New execute method in SvnRemoveCommand using a new ScmRemoveParameters carrying this new parameter.  If true, use url from repository as base to construct targets from scm file set in command line.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)