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

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

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

Robert Scholte moved MRELEASE-809 to SCM-706:
---------------------------------------------

           Complexity: Intermediate
          Component/s:     (was: Git)
                       maven-scm-provider-git
    Affects Version/s:     (was: 2.3.2)
                       1.8.1
                  Key: SCM-706  (was: MRELEASE-809)
              Project: Maven SCM  (was: Maven 2.x Release Plugin)
    
> 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
>         Attachments: 0001-MRELEASE-809-Use-git-correctly-when-removing-and-add.patch
>
>
> 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 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