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

ASF GitHub Bot commented on SCM-917:
------------------------------------

jira-importer commented on issue #1136:
URL: https://github.com/apache/maven-scm/issues/1136#issuecomment-2964647726

   **[Clemens 
Quoß](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cquoss)** 
commented
   
   Another argument is that there is no tag command in subversion, too.  
Tagging is done by copying from trunk to tags.  So 'untag' would be remove from 
tags.  If the the API should be complete, we would have to implement untag for 
subversion by using remove in the background. 
   




> Allow tags to be removed with Subversion implementation
> -------------------------------------------------------
>
>                 Key: SCM-917
>                 URL: https://issues.apache.org/jira/browse/SCM-917
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.11.1
>            Reporter: Clemens Quoß
>            Assignee: Michael Osipov
>            Priority: Critical
>             Fix For: 1.11.2
>
>         Attachments: git-diff-master.out, image-2019-02-02-16-57-33-664.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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.
> [UPDATE] - Implementation of scm:untag command will now be the target of this 
> issue (follow comment discussion)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to