[
https://issues.apache.org/jira/browse/SCM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962582#comment-17962582
]
ASF GitHub Bot commented on SCM-686:
------------------------------------
jira-importer commented on issue #899:
URL: https://github.com/apache/maven-scm/issues/899#issuecomment-2964631924
**[Christoph
Kutzinski](https://issues.apache.org/jira/secure/[email protected])**
commented
BTW: I've tried to use it via
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.4.1</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-api</artifactId>
<version>1.8.1</version>
<scope>compile</scope>
</dependency>
</dependencies>
</plugin>
and still run into this issue.
> 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)
