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 Sat, 02 Feb 2019 21:18:00 GMT

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

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

One more thing, Michael: We have a heavily customized maven-release, version 2.0-beta-9, that
we use for almost 10 years now.  Especially we did not like that all the tags in subversion
were saved directly under .../tags/....  For our new projects we would like to make use of
the tagBase parameter.  Looking at the documentation, scm:tag should heed this parameter
for svn, but  looking at TagMojo.java tells me otherwise.  Am I missing something here? 
 

> 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: 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