You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Brian Jackson (JIRA)" <ji...@codehaus.org> on 2010/04/01 18:40:22 UTC

[jira] Reopened: (SCM-363) Perforce Provider ignores p4 errors from stderr

     [ http://jira.codehaus.org/browse/SCM-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Jackson reopened SCM-363:
-------------------------------


As of 1.2 this patch seems to have been reversed and removed from the source.  Can someone explain?  Was there a regression or blocking issue?

> Perforce Provider ignores p4 errors from stderr
> -----------------------------------------------
>
>                 Key: SCM-363
>                 URL: http://jira.codehaus.org/browse/SCM-363
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-perforce
>            Reporter: Brian Jackson
>            Assignee: Emmanuel Venisse
>             Fix For: 1.1
>
>         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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira