[jira] [Updated] (SCM-706) prepare-with-pom deletes release-pom.xml then tries to git add it (presumably so the next commit records the fact)

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SCM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated SCM-706:
-------------------------------
    Fix Version/s: waiting-for-feedback

> 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://issues.apache.org/jira/browse/SCM-706
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.8.1
>            Reporter: Darryl L. Miles
>            Assignee: Mark Struberg
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>         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
(v7.6.3#76005)