You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maciej Matys (JIRA)" <ji...@codehaus.org> on 2014/01/14 14:52:50 UTC
[jira] (MRELEASE-539) prepare-with-pom fails for git provider
[ https://jira.codehaus.org/browse/MRELEASE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338671#comment-338671 ]
Maciej Matys commented on MRELEASE-539:
---------------------------------------
next commit "[maven-release-plugin] prepare for next development iteration" should remove added release-pom.xml's and bump versions.
> prepare-with-pom fails for git provider
> ---------------------------------------
>
> Key: MRELEASE-539
> URL: https://jira.codehaus.org/browse/MRELEASE-539
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: Git, prepare-with-pom
> Affects Versions: 2.0
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira