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

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/22 00:01:17 UTC

[jira] Updated: (SUREFIRE-187) using forkMode pertest , no log4j output in the console

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

Brett Porter updated SUREFIRE-187:
----------------------------------

    Affects Version/s: 1.5.1 (2.1.1 plugin)

> using forkMode pertest , no log4j output in the console
> -------------------------------------------------------
>
>                 Key: SUREFIRE-187
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-187
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 1.5.1 (2.1.1 plugin)
>         Environment: all
>            Reporter: Olivier Lamy
>         Assigned To: Carlos Sanchez
>
> When using forkMode pertest , no log4j or other output in the console.

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