[ 
https://jira.codehaus.org/browse/MRELEASE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darryl L. Miles updated MRELEASE-807:
-------------------------------------

    Attachment: 0001-MRELEASE-807-fix-so-that-tags-are-always-pushed-unam.patch

A patch again GIT tree maven-scm.git master c96ca234
                
> Git pushes tag ambigiously
> --------------------------
>
>                 Key: MRELEASE-807
>                 URL: https://jira.codehaus.org/browse/MRELEASE-807
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: Git, scm
>    Affects Versions: 2.3.2
>            Reporter: Darryl L. Miles
>            Priority: Minor
>         Attachments: 
> 0001-MRELEASE-807-fix-so-that-tags-are-always-pushed-unam.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://g...@git.domain.com/foobar.git root-0.0.1
> This is GOOD form:
> ssh push ssh://g...@git.domain.com/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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to