[
https://issues.apache.org/jira/browse/SCM-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961823#comment-17961823
]
ASF GitHub Bot commented on SCM-502:
------------------------------------
jira-importer opened a new issue, #714:
URL: https://github.com/apache/maven-scm/issues/714
**[Mark
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
opened
**[SCM-502](https://issues.apache.org/jira/browse/SCM-502?redirect=false)** and
commented
Calling scm:checkout for a tag often results in a merge failure.
This is caused by the fact that we do a git-pull prior to the checkout, but
in fact for tags, we only shall do a git-fetch.
This is due to the fact that the tag may be on a different branch, so
merging this branch into the current branch in the local repository would
destroy the local repository.
Instead we should first do a git-fetch [fetchUrl] followed by a git-checkout
tagname.
This will create a 'detached HEAD' in the local repo which is exactly the
way it should be in git.
---
**Affects:** 1.2
> checking out a tag from a remote repository fails if the tag was not on the
> current branch
> ------------------------------------------------------------------------------------------
>
> Key: SCM-502
> URL: https://issues.apache.org/jira/browse/SCM-502
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.2
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 1.3
>
>
> Calling scm:checkout for a tag often results in a merge failure.
> This is caused by the fact that we do a git-pull prior to the checkout, but
> in fact for tags, we only shall do a git-fetch.
> This is due to the fact that the tag may be on a different branch, so merging
> this branch into the current branch in the local repository would destroy the
> local repository.
> Instead we should first do a git-fetch [fetchUrl] followed by a git-checkout
> tagname.
> This will create a 'detached HEAD' in the local repo which is exactly the way
> it should be in git.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
