You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2006/01/11 23:43:05 UTC
[jira] Created: (MSUREFIRE-42) using forkMode pertest , no log4j
output in the console
using forkMode pertest , no log4j output in the console
-------------------------------------------------------
Key: MSUREFIRE-42
URL: http://jira.codehaus.org/browse/MSUREFIRE-42
Project: Maven 2.x Surefire Plugin
Type: Bug
Versions: 2.1.1
Environment: all
Reporter: Olivier Lamy
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MSUREFIRE-42) using forkMode pertest , no log4j
output in the console
Posted by "Mike Whittemore (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-42?page=comments#action_57363 ]
Mike Whittemore commented on MSUREFIRE-42:
------------------------------------------
I recently switched to using forkMode once and have the same problem: no log4j console output. My guess is its related to MSUREFIRE-53.
> using forkMode pertest , no log4j output in the console
> -------------------------------------------------------
>
> Key: MSUREFIRE-42
> URL: http://jira.codehaus.org/browse/MSUREFIRE-42
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.1.1
> Environment: all
> Reporter: Olivier Lamy
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MSUREFIRE-42) using forkMode pertest , no log4j
output in the console
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-42?page=all ]
Carlos Sanchez closed MSUREFIRE-42:
-----------------------------------
Assign To: Carlos Sanchez
Resolution: Duplicate
> using forkMode pertest , no log4j output in the console
> -------------------------------------------------------
>
> Key: MSUREFIRE-42
> URL: http://jira.codehaus.org/browse/MSUREFIRE-42
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.1.1
> Environment: all
> Reporter: Olivier Lamy
> Assignee: 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org