You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Mike Whittemore (JIRA)" <ji...@codehaus.org> on 2006/03/01 22:15:06 UTC
[jira] Commented: (MSUREFIRE-53) Make forked mode console output
look the same as non-forked mode console output
[ http://jira.codehaus.org/browse/MSUREFIRE-53?page=comments#action_59830 ]
Mike Whittemore commented on MSUREFIRE-53:
------------------------------------------
I have built the latest plugin from subversion (2.1.3-SNAPSHOT), see some improved output (test summaries), and see output from stdout and stderr in the test reports. However, I still do not see log4j output, even though I've configured log4j to output to the console with full debug turned on. See MSUREFIRE-42, which is marked as a duplicate of this issue and describes loss of log5j output.
I've tested this with forkMode=none as well as also do not see log4j output. Can anyone confirm whether the log4j portion of this issue is in fact fixed?
> Make forked mode console output look the same as non-forked mode console output
> -------------------------------------------------------------------------------
>
> Key: MSUREFIRE-53
> URL: http://jira.codehaus.org/browse/MSUREFIRE-53
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Fix For: 2.1.3
>
>
> Right now nothing comes out on the console which is confusing to users.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org