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

ASF GitHub Bot commented on SCM-705:
------------------------------------

jira-importer commented on issue #911:
URL: https://github.com/apache/maven-scm/issues/911#issuecomment-2964632578

   **[Darryl L. 
Miles](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dlmiles)** 
commented
   
   Another patch to apply AS WELL AS the 1st patch.
   
   GIT tree maven-scm.git master c96ca234
   
   This addresses a similar matter in respect of creating new branches on the 
remote system. Without the patch a conflict may occur of a branch and a tag 
share the same name.  With this patch we are being very clear to the server 
what the intention is, i.e. to work with branches (not with tags).
   
   See the other patch file for when we want to work with tags (not with 
branches).
   
   




> Git pushes tag ambigiously
> --------------------------
>
>                 Key: SCM-705
>                 URL: https://issues.apache.org/jira/browse/SCM-705
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.8.1
>            Reporter: Darryl L. Miles
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: 1.9
>
>         Attachments: 
> 0001-MRELEASE-807-fix-so-that-tags-are-always-pushed-unam.patch, 
> 0002-MRELEASE-807-also-disambiguate-push-commands-when-cr.patch, 
> 0003-MRELEASE-807-also-disambiguate-push-commands-when-cr.patch
>
>
> When the "git push" is run to push the new tag to the repo is uses the 
> ambigious form of just "root-0.0.1" where ${project.artifactId}=root and 
> ${project.version}=0.0.1
> Like this is BAD form:
> ssh push ssh://[email protected]/foobar.git root-0.0.1
> This is GOOD form:
> ssh push ssh://[email protected]/foobar.git refs/tags/root-0.0.1
> To test this problem out simple create a new branch with the same name as the 
> tag you are about to use.
> git branch root-0.0.1
> git push origin root-0.0.1
> git branch -av
> Now use the maven-release-plugin to try to make a git tag called 'root-0.0.1'.
> So it is correct to prefix the tags you push with the "refs/tags/" to that 
> the repository know you are sending up a tag.  This is never ambiguous.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to