[
https://issues.apache.org/jira/browse/SCM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962577#comment-17962577
]
ASF GitHub Bot commented on SCM-686:
------------------------------------
jira-importer opened a new issue, #899:
URL: https://github.com/apache/maven-scm/issues/899
**[Ralf
Thielow](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ralf.thielow)**
opened
**[SCM-686](https://issues.apache.org/jira/browse/SCM-686?redirect=false)** and
commented
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
---
**Affects:** 1.7
**Attachments:**
-
[git-status-use-porcelain-option.diff](https://issues.apache.org/jira/secure/attachment/12718775/git-status-use-porcelain-option.diff)
(_11.97 kB_)
**Issue Links:**
- [SCM-738](https://issues.apache.org/jira/browse/SCM-738) GitStatusConsumer
fails to correctly parse git 1.8.5 status output
(_**"is duplicated by"**_)
- [SCM-709](https://issues.apache.org/jira/browse/SCM-709) REGRESSION: git
status doesn't work if repository root is not the working directory
- [MRELEASE-812](https://issues.apache.org/jira/browse/MRELEASE-812)
"prepare" does not commit before tagging and therefore deploys snapshot instead
of release
> Maven SCM failed to parse "git status" output if git messages are translated
> ----------------------------------------------------------------------------
>
> Key: SCM-686
> URL: https://issues.apache.org/jira/browse/SCM-686
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.7
> Environment: Ubuntu Linux 11.10, Maven-3.0.4
> Reporter: Ralf Thielow
> Assignee: Olivier Lamy
> Priority: Critical
> Fix For: 1.8
>
> Attachments: git-status-use-porcelain-option.diff
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)