[jira] Updated: (SUREFIRE-174) Various information is written to stdout instead of log which is not embedder-friendly

2007-02-22 Thread Brett Porter (JIRA)

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

Brett Porter updated SUREFIRE-174:
--

Fix Version/s: (was: 2.3)
   2.4

 Various information is written to stdout instead of log which is not 
 embedder-friendly
 --

 Key: SUREFIRE-174
 URL: http://jira.codehaus.org/browse/SUREFIRE-174
 Project: Maven Surefire
  Issue Type: Bug
Reporter: Stepan Roh
 Fix For: 2.4


 The information (known to me) written to stdout in maven-surefire-plugin-2.2 
 and surefire-booter-2.0 is:
 - SurefireBooter writes Forking command line... if debug is enabled
 - SurefireBooter redirects stdout and stderr of forked process to stdout 
 (this one is most serious, I think)
 - SurefirePlugin outputs summary and/or text report to console (I know it can 
 be switched off and/or written to file, but I would like to have it written 
 to log)
 It is important to have all this information written to log instead of 
 stdout, because information is lost if written to console and embedder is 
 used (two or more embedders may run and confuse their output) and it is also 
 important to be able to align such information with information already 
 logged.

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




[jira] Updated: (SUREFIRE-174) Various information is written to stdout instead of log which is not embedder-friendly

2007-01-23 Thread Brett Porter (JIRA)

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

Brett Porter updated SUREFIRE-174:
--

Fix Version/s: 2.3

 Various information is written to stdout instead of log which is not 
 embedder-friendly
 --

 Key: SUREFIRE-174
 URL: http://jira.codehaus.org/browse/SUREFIRE-174
 Project: Maven Surefire
  Issue Type: Bug
Reporter: Stepan Roh
 Fix For: 2.3


 The information (known to me) written to stdout in maven-surefire-plugin-2.2 
 and surefire-booter-2.0 is:
 - SurefireBooter writes Forking command line... if debug is enabled
 - SurefireBooter redirects stdout and stderr of forked process to stdout 
 (this one is most serious, I think)
 - SurefirePlugin outputs summary and/or text report to console (I know it can 
 be switched off and/or written to file, but I would like to have it written 
 to log)
 It is important to have all this information written to log instead of 
 stdout, because information is lost if written to console and embedder is 
 used (two or more embedders may run and confuse their output) and it is also 
 important to be able to align such information with information already 
 logged.

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