[arquillian-issues] [JBoss JIRA] (ARQ-710) Separated per-test and per-container log files.

[Ondrej Zizka (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652972#comment-12652972 ] 

Ondrej Zizka commented on ARQ-710:
----------------------------------

How about writing an Appender which would somehow be able to receive an event from arquillian, upon which it would shift the log file, like *RollingAppender's do.

For example: Arquillian could set a system property with the name of the test being run. The appender would shift the files when this property changed. I'm not sure if it's possible to set sys prop for a running JVM, so it could also be set through AS management.
                
> Separated per-test and per-container log files.
> -----------------------------------------------
>
>                 Key: ARQ-710
>                 URL: https://issues.jboss.org/browse/ARQ-710
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Base Implementation
>    Affects Versions: 1.0.0.CR7
>            Reporter: Ondrej Zizka
>            Priority: Critical
>
> What's the best way to separate server and client log messages?
> Currently, any output is redirected to Surefire. Which only creates one output.
> So, either arq can log to an arbitrary file, or surefire could have support for multiple logs.
> The later won't happen any soon I guess Arq just forwards anything to surefire.
> So, let's say I want to have separated log files in surefire-reports dir:
> * org.jboss.FooBarTestCase-client,
> * org.jboss.FooBarTestCase-server1,
> * org.jboss.FooBarTestCase-server2, ...
> This feature is quite important for large testsuites which produce tons of log messages,
> and even more for multi-node tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira