p4 command reports most or all errors on stderr but maven-scm-provider-perforce 
throws away stderr
--------------------------------------------------------------------------------------------------

                 Key: MPSCM-90
                 URL: http://jira.codehaus.org/browse/MPSCM-90
             Project: maven-scm-plugin
          Issue Type: Bug
         Environment: I tested this with whatever version came down by default 
& then with the lastest svn trunk. The fixes & affects versions available in 
this issue form don't seem to match the versions available.

[EMAIL PROTECTED] maven-scm-provider-perforce]$ p4 -V
Perforce - The Fast Software Configuration Management System.
Copyright 1995-2006 Perforce Software.  All rights reserved.
Rev. P4/LINUX24X86/2006.1/101890 (2006/06/21).

[EMAIL PROTECTED] maven-scm-provider-perforce]$ p4 info
User name: tparker
Client name: tua
Client host: tua.uiactive.com
Client unknown.
Current directory: 
/u01/tomp/maven-scm/maven-scm-providers/maven-scm-provider-perforce
Client address: 172.18.1.29:52715
Server address: sydb.bullant.local:1666
Server root: P:\P4ROOT
Server date: 2006/10/31 16:47:50 +1100 AUS Eastern Daylight Time
Server version: P4D/NTX86/2005.2/93627 (2006/02/14)
Server license: Bullant Software (fka Bullant Technology - fna Softblocks Pty.) 
40 users (support expired 2006/10/04)

            Reporter: Tom Parker
         Attachments: maven-scm-provider-perforce.patch

This applies to most or all commands in maven-scm-provider-perforce. I was 
unable to fix some basic scm configuration issues until I downloaded the 
maven-scm-provider-perforce source and hacked it to consume and report the p4 
command's stderr as well as stdout.

The attached patch fixes the problem for diff, checkin, checkout and tag. My 
solution naively consumes stdout until it is finished and then consums stderr. 
This isn't ideal if the output order is significant, but for the errors 
situations I was dealing with, it worked fine. I had a brief search for an 
InputStreamMultiplexer but found nothing. I have included todos to improve this.

There is much potential for reuse between the classes in 
maven-scm-provider-perforce, I have included todo's stating as such.

I have not fixed all the perforce commands. Sorry.

-- 
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

        

Reply via email to