[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=12654669#comment-12654669 ] 

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

I've created a logged which would do that: https://github.com/OndraZizka/jboss-as/compare/TS-logPerTest   (not tested)

Now it's up to ARQ AS7 container to set the properties properly.
                
> 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, log messages can either go to the console, and Arquillian "forwards" them to Surefire, which causes mixed client and server messages.
> Or, messages can go to the server log file as usually. Which ends up in tens of megabytes long log files.
> 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