[
https://issues.apache.org/jira/browse/SCM-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963058#comment-17963058
]
ASF GitHub Bot commented on SCM-240:
------------------------------------
jira-importer commented on issue #1001:
URL: https://github.com/apache/maven-scm/issues/1001#issuecomment-2964638411
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
This issue has been auto closed because it has been inactive for a long
period of time. If you think this issue still applies, retest your problem with
the most recent version of Maven and the affected component, reopen and post
your results.
> add support for tagging a revision
> ----------------------------------
>
> Key: SCM-240
> URL: https://issues.apache.org/jira/browse/SCM-240
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-plugin, maven-scm-api
> Reporter: Sharmarke Aden
> Priority: Major
>
> I am not sure if this functionality can be supported by all scm providers but
> in subversion one can tag a revision using the copy command. I would love to
> see support added to SCM so that a) one can determine the current working
> revision and b) based on the working revision ID create a tag. In subversion
> on can do this by using the following set of commands.
> #get the working copy revision information
> svn info
> #create a tag from the trunk using revision 1204
> svn copy -r1204 http://svn.example.com/repos/calc/trunk
> http://svn.example.com/repos/calc/tags/release-1.0 -m "revision tag"
> Notes:
> My understanding is that SCM API currently does support getting the revision
> of the current working copy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
