commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <>
Subject Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
Date Mon, 17 May 2004 20:49:49 GMT
At 10:33 PM 5/17/2004, Mario Ivankovits wrote:

>The change was in the Category class, formerly the log methods accepted a 
>priority but this has change to a level now.
>But it looks like the change isnt really backward compatible, i have tried 
>this now and got the following exception (patched commons-logging and 
>    at org.apache.commons.logging.impl.Log4JLogger.fatal(
>    at org.apache.commons.vfs.test.RunTest.main(
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>    at 
> sun.reflect.NativeMethodAccessorImpl.invoke(
>    at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
>    at java.lang.reflect.Method.invoke(
>    at com.intellij.rt.execution.application.AppMain.main(Unknown Source)

The above looks wrong to me. Are you sure you don't have stale classes 
around during compilation?

>Maybe we relly need a new Log4J implementation depending on its version 
>.... this is bad, isnt it?

Don't gump the gun yet.

Ceki Gülcü

      For log4j documentation consider "The complete log4j manual"
      ISBN: 2970036908  

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message