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 log4j-1.2.8):
java.lang.NoSuchMethodError: org.apache.log4j.Logger.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V
at org.apache.commons.logging.impl.Log4JLogger.fatal(Log4JLogger.java:161)
at org.apache.commons.vfs.test.RunTest.main(RunTest.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
