[
http://jira.codehaus.org/browse/SUREFIRE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127999
]
Herve Boutemy commented on SUREFIRE-174:
----------------------------------------
can you check if the problems are still here with 2.4?
then please explain how to reproduce problems (what is expected precisely, and
what is obtained)
> 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.x
>
>
> 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
