[MRELEASE-887] using pomFileName with git, prepare neglects to commit (or push)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.5
• Component/s: Git
• Assignee: Benson Margulies
• Reporter: Benson Margulies
• Created: 10/Sep/14 13:01
• Updated: 10/Sep/14 13:07
• Resolved: 10/Sep/14 13:07

Description

Using the test project at [e-mail]:bimargulies/pom-file-name-tc.git, with

git --version
git version 1.8.5.2 (Apple Git-48)

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:

[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.

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.

Issue Links

• duplicates: MRELEASE-875 release:prepare does not commit pom.xml if not in the git root