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

Olivier Lamy commented on SCM-240:
----------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-scm#1001|https://github.com/apache/maven-scm/issues/1001]. 

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

Reply via email to