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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 2.5.1
• Component/s: prepare, scm
• Environment: git 1.9.0
• Assignee: Benson Margulies
• Reporter: john ten Den
• Created: 10/Apr/14 09:23
• Updated: 06/Apr/15 01:08
• Resolved: 17/Sep/14 09:33

Description

When the project pom.xml is not in the Git project root (f.e. in the "src" directory) the pom.xml not committed and pushed (before tagging)
Commit of the pom.xml during release:prepare works fine if it is in the / (root) of the git repository
Using the pom.xml in a subdirectory worked well with version 2.4.2 using git 1.7.

Issue Links

• is duplicated by: MRELEASE-885 When the base pom is a subdirectory, tagging fails in GIT
• is duplicated by: MRELEASE-887 using pomFileName with git, prepare neglects to commit (or push)
• is related to: MRELEASE-812 "prepare" does not commit before tagging and therefore deploys snapshot instead of release
• is related to: SCM-740 Maven Release Plugin releases SNAPSHOT instead of STABLE version
• is related to: MRELEASE-883 Upgrade SCM to 1.9.1
• relates to: MRELEASE-812 "prepare" does not commit before tagging and therefore deploys snapshot instead of release