[
https://jira.jboss.org/jira/browse/JGRP-851?page=com.atlassian.jira.plugi...
]
Richard Achmatowicz commented on JGRP-851:
------------------------------------------
Implementation is completed. Here is an example of the output:
org.jgroups.tests.LostOutputTest:
Calling setUp()
with more text
with more text
with more text
with more text
0 [WARN] LostOutputTest: - setUp()
3 [WARN] LostOutputTest: - test0
Calling test0
44 [WARN] LostOutputTest: - tearDown()
Calling tearDown()
Calling setUp()
with more text
with more text
with more text
with more text
46 [WARN] LostOutputTest: - setUp()
50 [WARN] LostOutputTest: - test1
Calling test1
51 [WARN] LostOutputTest: - tearDown()
Calling tearDown()
Integrate commons-logging output with testNG test case reports
--------------------------------------------------------------
Key: JGRP-851
URL:
https://jira.jboss.org/jira/browse/JGRP-851
Project: JGroups
Issue Type: Bug
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Priority: Minor
Fix For: 2.7
At present, logging output from commons-logging gets directed by the ConsoleAppender to
the console. This is unfortunate for two reasons: (i) as the output from a testNG test
case (collected by org.jgroups.util.JUnitXMLReporter) and the logging output are now not
collected together and (ii) the logging output is effectively lost when the console dies.
Need to find a way to cause the commons-logging output (which is supported by a log4j
implementation) to be collected together with the test cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira