maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clemens Quoß (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SCM-917) Implement scm:untag for Subversion provider
Date Sun, 03 Feb 2019 23:21:00 GMT

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

Clemens Quoß commented on SCM-917:
----------------------------------

Michael, since this is my first time doing some work here, this is what I did:
- created a branch locally called 'SCM-917'
- implemented what I think needs to be done for scm:untag for svn
- created a diff file which I uploaded here
Could you please check if I am on the right track?  What is still needed is implementing
the tck test for svn.
When everything is complete, who would I have to send the patch to?  Who is the committer
for maven-scm?
TIA Clemens

> Implement scm:untag for Subversion provider
> -------------------------------------------
>
>                 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: git-diff-master.out, 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.
> [UPDATE] - Implementation of scm:untag command will now be the target of this issue
(follow comment discussion)



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

Mime
View raw message