Benson Margulies created MRELEASE-887:
-----------------------------------------
Summary: using pomFileName with git, prepare neglects to commit
(or push)
Key: MRELEASE-887
URL: https://jira.codehaus.org/browse/MRELEASE-887
Project: Maven Release Plugin
Issue Type: Bug
Components: Git
Affects Versions: 2.5
Reporter: Benson Margulies
Using the test project at [email protected]:bimargulies/pom-file-name-tc.git, with
{noformat}
git --version
git version 1.8.5.2 (Apple Git-48)
{noformat}
if I cd into the 'second' directory, and run mvn release:perform --batch-mode,
it edits the pom but does not commit the edit.
Here's some console output:
{noformat}
[INFO] Not removing release POMs
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /Users/benson/misc/pom-file-name-tc/second &&
git add -- pom.xml
[INFO] Working directory: /Users/benson/misc/pom-file-name-tc/second
[INFO] Executing: /bin/sh -c cd /Users/benson/misc/pom-file-name-tc/second &&
git rev-parse --show-toplevel
[INFO] Working directory: /Users/benson/misc/pom-file-name-tc/second
[INFO] Executing: /bin/sh -c cd /Users/benson/misc/pom-file-name-tc/second &&
git status --porcelain .
[INFO] Working directory: /Users/benson/misc/pom-file-name-tc/second
[WARNING] Ignoring unrecognized line: ?? second/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? second/release.properties
[INFO] Release preparation complete.
{noformat}
git reflog shows no relevant commits. A useless tag does get created pointing
to a snapshot.
This seems very familiar for older versions of the release plugin, but I've
only seen it with the use of pomFileName for release 2.5.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)