[
https://issues.apache.org/jira/browse/SCM-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961170#comment-17961170
]
ASF GitHub Bot commented on SCM-363:
------------------------------------
jira-importer opened a new issue, #582:
URL: https://github.com/apache/maven-scm/issues/582
**[Brian
Jackson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jaxzin)**
opened
**[SCM-363](https://issues.apache.org/jira/browse/SCM-363?redirect=false)** and
commented
All of the perforce commands are implemented to only check stdout for errors
when the errors are actually written to stderr. Attached is a patch for a
subset of the commands.
---
**Attachments:**
-
[stderrChecking.patch](https://issues.apache.org/jira/secure/attachment/12718842/stderrChecking.patch)
(_13.30 kB_)
**Issue Links:**
- [SCM-501](https://issues.apache.org/jira/browse/SCM-501) Perforce Provider
ignores p4 errors from stderr
(_**"is duplicated by"**_)
> Perforce Provider ignores p4 errors from stderr
> -----------------------------------------------
>
> Key: SCM-363
> URL: https://issues.apache.org/jira/browse/SCM-363
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Reporter: Brian Jackson
> Assignee: Emmanuel Venisse
> Priority: Major
> Attachments: stderrChecking.patch
>
>
> All of the perforce commands are implemented to only check stdout for errors
> when the errors are actually written to stderr. Attached is a patch for a
> subset of the commands.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
