[SCM-686] Maven SCM failed to parse "git status" output if git messages are translated

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.7
• Fix Version/s: 1.8
• Component/s: maven-scm-provider-gitexe
• Environment: Ubuntu Linux 11.10, Maven-3.0.4
• Flags: Patch
• Assignee: Olivier Lamy
• Reporter: Ralf Thielow
• Created: 20/Aug/12 09:15
• Updated: 05/Apr/15 14:53
• Resolved: 20/Aug/12 11:10

Description

Maven SCM failed to parse "git status" output if git messages are
translated. This breaks at least maven-release plugin.
The issue is that GitStatusConsumer uses regular expressions to
parse the output of "git status" and these regexps don't match
anymore if git messages are translated. In order to avoid this, we
should use the "--porcelain" option on "git status" to produce
a machine readable output which can be parsed even if git messages
are translated.
I've attached a patch which solves the problem.

Ralf

Issue Links

• is duplicated by: SCM-738 GitStatusConsumer fails to correctly parse git 1.8.5 status output
• is related to: SCM-709 REGRESSION: git status doesn't work if repository root is not the working directory
• is related to: MRELEASE-812 "prepare" does not commit before tagging and therefore deploys snapshot instead of release