[
https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.sy...
]
Ondrej Zizka commented on ARQ-710:
----------------------------------
Aslak:
{quote}
Not sure how to attack this.. in theory the stream that is wrapped in the managed
container should be able to tell you which server it's from, so hench could be
redirected somewhere, but not sure how to get 'client'.
In AS4-6 CONSOLE was just another logger, i'm sure AS7 is similar. Wouldn't
setting server1, server2 to log to specific file get you what you want? If no server logs
to CONSOLE, then the assumption is the rest is 'client' ?
{quote}
I thought about that, but that would only separate by server. I believe it would be very
convenient if separated by server _and_ test.
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