logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <nore...@qos.ch>
Subject Re: Solution to defect 18875 breaks other projects
Date Wed, 08 Sep 2004 13:11:41 GMT

At 02:48 PM 9/8/2004, logging@fam-homeijer.demon.nl wrote:
> >From defect 18875:
>Solution: Remove the static fields Priority.DEBUG through Priority.FATAL
>I think this would break a lot of projects dependend on log4j. Wouldn't it 
>be more wise to
>deprecate the static fields or changed into "public static final Level 
>WARN = Level.WARN"
>(could cause inheritance problems)?

Have you looked at the code currently in CVS? Observe that the Priority 
class is just:

public class Priority extends Level {

In other words, Priority extends Level. For example, you can access the 
DEBUG level by writing

>It immediately breaks the Log4JLogger from commons-logging and would 
>probably mean a more
>difficult migration when switching from 1.2.8 to 1.3.

It immediately breaks Log4JLogger from commons-logging? Which version of 
c-l are you referring to? CL version 1.0.4 is known to be compatible with 
both log4j 1.2.x and 1.3.


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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message