maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SCM-917) Implement scm:untag for Subversion provider
Date Wed, 06 Feb 2019 08:12:00 GMT

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

Michael Osipov commented on SCM-917:
------------------------------------

Let me guide you:
 * Fork the repo on GH
 * Clone the repo locally
 * Create the branch SCM-917
 * Do the magic
 * Review and create a PR

Magic: Change/add the code which is necessary to solve the problem. Tests are requires. You
can use the Git tests (flow) or any other Subversion test as an example. That will suffice.
Don't change unrelated parts. I. .e, if you want to fix the JGit stuff, create another ticket
and branch for it.

> 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