[ https://issues.apache.org/jira/browse/SCM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536337#comment-14536337 ]
ASF GitHub Bot commented on SCM-795: ------------------------------------ GitHub user ChrisGWarp opened a pull request: https://github.com/apache/maven-scm/pull/34 [SCM-795] Fixed. Content on stderr will no longer raise an exception. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ChrisGWarp/maven-scm SCM-795 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-scm/pull/34.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #34 ---- commit 2d7502077559d46f8009e45311b8ce5ab79f01bb Author: Chris Graham <chrisgw...@apache.org> Date: 2015-05-09T10:06:36Z [SCM-795] Fixed. Content on stderr will no longer raise an exception. ---- > scm output parsing is too aggressive on stderr > ---------------------------------------------- > > Key: SCM-795 > URL: https://issues.apache.org/jira/browse/SCM-795 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-jazz > Affects Versions: 1.9.2 > Environment: All. > Reporter: Chris Graham > Assignee: Chris Graham > 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 (v6.3.4#6332)