On Tue, 2006-02-28 at 22:59 +0000, robert burrell donkin wrote: > On Tue, 2006-02-28 at 23:39 +0100, Jean-frederic Clere wrote: > > Hi, > > > > I am trying logging + log4j with harmony jchevm but when I am using > > commons-logging-1.0.4 and logging-log4j-1.2.13 > > I have an exception: > > +++ > > java.lang.NoSuchMethodError: > > org/apache/log4j/Category.log(Ljava/lang/String;Lorg/apache/log4j/Level;Ljava/lang/Object;Ljava/lang/Throwable;)V > > at java.lang.VMThrowable.fillInStackTrace(Native Method) > > at java.lang.Throwable.fillInStackTrace(Throwable.java:498) > > at java.lang.Throwable.<init>(Throwable.java:159) > > at java.lang.Error.<init>(Error.java:81) > > at java.lang.LinkageError.<init>(LinkageError.java:72) > > at > > java.lang.IncompatibleClassChangeError.<init>(IncompatibleClassChangeError.java:71) > > at java.lang.NoSuchMethodError.<init>(NoSuchMethodError.java:72) > > at java.lang.VMClass.forName(Native Method) > > at java.lang.Class.forName(Class.java:161) > > at toto.main(toto.java:8) > > +++ > > If I am using logging-log4j-1.3alpha-8 jchevm works ok. > > > > Any idea why commons-logging-1.0.4 requires a 1.3x log4j? > > nope, none at all > > could you retry with the latest release candidate from the 1.1 > codestream? > > http://people.apache.org/~rdonkin/commons-logging/
While it would be nice to have testing with 1.1, we should figure out what's going on here too. Initially it looks to me like the log4j team have accidentally made a 1.2.13 release which is binary-incompatible with 1.2.12. If that proves to be the case we need to tell them so they can fix this. Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
