[jboss-dev] Added Log4jConsoleLoggingPlugin to jboss-test

Scott M Stark scott.stark at jboss.org
Thu Oct 5 08:27:20 EDT 2006


That was not the only source of a log4j configuration.

Adrian Brock wrote:
> This is because somebody has added system/src/resources to the
> eclipse classpath.
>
> This needs to be src/resources/tests.
>
> I'm going to remove it and whoever did it can fix it properly.
>
> On Sun, 2006-10-01 at 16:43 -0700, Scott M Stark wrote:
>   
>> 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();
>>    }
>>
>>     




More information about the jboss-development mailing list