[
http://jira.codehaus.org/browse/MRELEASE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217162#action_217162
]
Maarten Billemont commented on MRELEASE-538:
--------------------------------------------
Invalid, see MRELEASE-539 instead.
> Release-with-pom fails for git provider
> ---------------------------------------
>
> Key: MRELEASE-538
> URL: http://jira.codehaus.org/browse/MRELEASE-538
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Reporter: Maarten Billemont
>
> When running the release-with-pom goal; toward the end, the release-poms are
> deleted and this change is committed. Unfortunately, with the GIT provider,
> this is done by first git rm'ing the files and then git add'ing them
> (presumably, to add the rm change to the index). The latter fails because
> the files are no longer present.
> {code}
> [INFO] Executing: /bin/sh -c cd /Users/lhunath/work/git && git rm
> release-pom.xml d/release-pom.xml c/release-pom.xml e/release-pom.xml
> [INFO] Working directory: /Users/lhunath/work/git
> [INFO] Checking in modified POMs...
> [INFO] Executing: /bin/sh -c cd /Users/lhunath/work/git && git add -- pom.xml
> release-pom.xml d/pom.xml d/release-pom.xml c/pom.xml c/release-pom.xml
> e/pom.xml e/release-pom.xml
> [INFO] Working directory: /Users/lhunath/work/git
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The git-add command failed.
> Command output:
> fatal: pathspec 'release-pom.xml' did not match any files
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
