I'm no expert on when to [or not to] cross post, but this looks like a good topic for discussion in these two places at once.
regards Adam ----- Original Message ----- From: "Mario Ivankovits" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> Sent: Monday, May 17, 2004 2:33 PM Subject: Re: [EMAIL PROTECTED]: jakarta-commons/commons-logging failed > robert burrell donkin wrote: > > > i am more than a little confused about this whole issue. i've taken a > > look in cvs and priority still seems to be in existence (and > > undeprecated). when i looked at the gump record for sunday, > > common-logging seems to have passed. can someone please either explain > > where the log4j changes are and when the failure occurred? > > > > (as for the suggested patch) i'd be very unhappy about committing a > > patch which broke backwards compatibility with the most common > > versions of log4j (especially this close to a release). in fact, i'd > > probably think about vetoing any such change. there are a number of > > important upcoming releases who would be directly effected by these > > changes as well as a very large number of users of these releases who > > would be forced to upgrade. > > > Ceki G�lc� wrote: > > > Fortunately, the required changes are easy and are backward compatible. > > Commons-logging code needs to be changed as follows. > > 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) > > Maybe we relly need a new Log4J implementation depending on its version > .... this is bad, isnt it? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
