[
https://jira.codehaus.org/browse/SCM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352283#comment-352283
]
Arthur Housinger edited comment on SCM-706 at 9/3/14 5:04 PM:
--------------------------------------------------------------
I created a testcase and uploaded it. The only difference between this and
what I actually tested is the "connection" tag.
BTW, any advice on working around the issue would be appreciated. As it
stands, it looks like our migration from svn to git is going to include
removing all of our calls to prepare:release-with-pom and replacing it with
some other mechanism (tbd).
was (Author: mistermouse):
testcase
> prepare-with-pom deletes release-pom.xml then tries to git add it (presumably
> so the next commit records the fact)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SCM-706
> URL: https://jira.codehaus.org/browse/SCM-706
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-git
> Affects Versions: 1.8.1
> Reporter: Darryl L. Miles
> Assignee: Mark Struberg
> Attachments:
> 0001-MRELEASE-809-Use-git-correctly-when-removing-and-add.patch, pom.xml
>
>
> When running: git release:prepare-with-pom
> After the tag is created and pushed, it then runs the sequence:
> git rm release-pom.xml
> git add -- pom.xml release-pom.xml
> But the "git add" fails because the "git rm" did the action of removing the
> actual file and adding the file removal fact to the cached index ready for
> the next commit to pickup.
> The solution is to remove the "release-pom.xml" argument from the "git add"
> it is unnecessary.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
