[
https://jira.codehaus.org/browse/SCM-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Miles updated SCM-705:
--------------------------------
Attachment: 0003-MRELEASE-807-also-disambiguate-push-commands-when-cr.patch
A 3rd patch to apply AS WELL AS the other 2 patches for another location that
can be disambiguated.
> Git pushes tag ambigiously
> --------------------------
>
> Key: SCM-705
> URL: https://jira.codehaus.org/browse/SCM-705
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.8.1
> Reporter: Darryl L. Miles
> Priority: Minor
> 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 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
