[
https://issues.apache.org/jira/browse/SCM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963105#comment-17963105
]
ASF GitHub Bot commented on SCM-795:
------------------------------------
jira-importer opened a new issue, #1018:
URL: https://github.com/apache/maven-scm/issues/1018
**[Chris
Graham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=chrisgwarp)**
opened
**[SCM-795](https://issues.apache.org/jira/browse/SCM-795?redirect=false)** and
commented
In some versions of the jazz client (scm.exe), which is a wrapper for a
headless eclipse runtime, there are some additional lines output to stderr
(about a JobManager still running or similar) but the scm.exe return code is
zero.
The parsing code is being too aggressive as it detects stderr output and
assumes (incorrectly in this case) an error. The return code should take
priority over the stderr output (which really should be ignored).
---
**Affects:** 1.9.2
> scm output parsing is too aggressive on stderr
> ----------------------------------------------
>
> Key: SCM-795
> URL: https://issues.apache.org/jira/browse/SCM-795
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-jazz
> Affects Versions: 1.9.2
> Environment: All.
> Reporter: Chris Graham
> Assignee: Chris Graham
> Priority: Major
> Fix For: 1.9.5
>
>
> In some versions of the jazz client (scm.exe), which is a wrapper for a
> headless eclipse runtime, there are some additional lines output to stderr
> (about a JobManager still running or similar) but the scm.exe return code is
> zero.
> The parsing code is being too aggressive as it detects stderr output and
> assumes (incorrectly in this case) an error. The return code should take
> priority over the stderr output (which really should be ignored).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
