You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Darryl L. Miles (JIRA)" <ji...@codehaus.org> on 2012/12/04 23:23:13 UTC
[jira] (MRELEASE-807) Git pushes tag ambigiously
Darryl L. Miles created MRELEASE-807:
----------------------------------------
Summary: 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
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://git@git.domain.com/foobar.git root-0.0.1
This is GOOD form:
ssh push ssh://git@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
[jira] (SCM-705) Git pushes tag ambigiously
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ 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://git@git.domain.com/foobar.git root-0.0.1
> This is GOOD form:
> ssh push ssh://git@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
[jira] (MRELEASE-807) Git pushes tag ambigiously
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darryl L. Miles updated MRELEASE-807:
-------------------------------------
Attachment: 0002-MRELEASE-807-also-disambiguate-push-commands-when-cr.patch
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: 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, 0002-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://git@git.domain.com/foobar.git root-0.0.1
> This is GOOD form:
> ssh push ssh://git@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
[jira] (MRELEASE-807) Git pushes tag ambigiously
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ 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://git@git.domain.com/foobar.git root-0.0.1
> This is GOOD form:
> ssh push ssh://git@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
[jira] (SCM-705) Git pushes tag ambigiously
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte moved MRELEASE-807 to SCM-705:
---------------------------------------------
Complexity: Intermediate
Component/s: (was: Git)
(was: scm)
maven-scm-provider-git
Affects Version/s: (was: 2.3.2)
1.8.1
Key: SCM-705 (was: MRELEASE-807)
Project: Maven SCM (was: Maven 2.x Release Plugin)
> 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
>
>
> 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://git@git.domain.com/foobar.git root-0.0.1
> This is GOOD form:
> ssh push ssh://git@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
[jira] (SCM-705) Git pushes tag ambigiously
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SCM-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed SCM-705.
----------------------------
Resolution: Fixed
Fix Version/s: 1.9
Assignee: Olivier Lamy
fixed https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=commit;h=f7b115ed0ca0f429b9fd644528211f66d008dbbf
Thanks !
> 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
> 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://git@git.domain.com/foobar.git root-0.0.1
> This is GOOD form:
> ssh push ssh://git@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