Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0
-
None
Description
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.
[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
Attachments
Issue Links
- supercedes
-
MRELEASE-538 Release-with-pom fails for git provider
- Closed