[jira] [Updated] (SCM-494) Let providers indicate whether a commit is required before a tag

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SCM-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated SCM-494:
-------------------------------
    Fix Version/s: waiting-for-feedback

> Let providers indicate whether a commit is required before a tag
> ----------------------------------------------------------------
>
>                 Key: SCM-494
>                 URL: https://issues.apache.org/jira/browse/SCM-494
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-api
>            Reporter: Mike Dillon
>            Priority: Minor
>             Fix For: waiting-for-feedback
>
>         Attachments: requiresCommitBeforeTag.diff
>
>
> As part of looking into creating a patch for MRELEASE-477, I realized that SCM providers would need to indicate whether they are able to create a "tag" directly from a modified working copy. Subversion can do this, but not all providers can. I'm providing a patch that adds a requiresCommitBeforeTag() method to ScmProvider, similar to the requiresEditMode() method. It looks like there is a request for a general "capabilities" API in SCM-23; this would fit into such an API if it existed, but that issue doesn't have a patch attached :)
> I haven't provided a test of this since it's only a flag that is not used inside maven-scm (I'm planning to provide a patch for maven-release to use it there). I could see it being used in scm:tag to allow a generic check for a dirty working copy in a local-to-remote tag operation, but it seems like these things are better handled by the provider themselves.



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