I was having problems with too many log4j resources being seen in
testcase classpaths and conflicting with the unit test output so I added
a org.jboss.test.logging.Log4jConsoleLoggingPlugin that simply
configures a console appender without looking for classpath resources.
Its in the current jboss-test snapshot versoin and can be installed
using the org.jboss.test.logging.LogginPlugin sys property in setUp:
@Override
protected void setUp() throws Exception
{
System.setProperty("org.jboss.test.logging.LogginPlugin",
"org.jboss.test.logging.Log4jConsoleLoggingPlugin");
super.setUp();
}