commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <>
Subject Re: [GUMP@brutus]: jakarta-commons/commons-logging failed
Date Mon, 17 May 2004 21:23:48 GMT

On 17 May 2004, at 21:33, Mario Ivankovits wrote:

> 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):

(as i read the language specification 2.0 anyway) this change should be 
compile compatible but not binary compatible. (i think that the cause 
is that in java the method overload algorithm is executed at compile 
time - see sections 13.2 and 15.2.)

nice if ceki (or someone else from log4j) could confirm that this 
change is incompatible.

- robert

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

View raw message