[
https://issues.apache.org/jira/browse/SCM-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961172#comment-17961172
]
ASF GitHub Bot commented on SCM-363:
------------------------------------
jira-importer commented on issue #582:
URL: https://github.com/apache/maven-scm/issues/582#issuecomment-2964605192
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and
proceed appropriately.
> 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)
