Same disclaimer:

 From 
http://logging.apache.org/log4j/docs/api/org/apache/log4j/Category.html

> This class has been deprecated and replaced by the Logger subclass. It 
> will be kept around to preserve backward compatibility until mid 2003.
>
>  Logger is a subclass of Category, i.e. it extends Category. In other 
> words, a logger is a category. Thus, all operations that can be 
> performed on a category can be performed on a logger. Whenever log4j 
> is asked to produce a Category object, it will instead produce a 
> Logger object. However, methods that previously accepted category 
> objects still continue to accept category objects.



On Oct 29, 2004, at 12:07 AM, Stefano Mazzocchi wrote:
>
>  3) if not, if you are willing to work with the offended dependees to 
> restore their success status.
>
>


It is late 2004 now.  It will be interesting to see how far the ripples 
go, but changing all references to org.apache.log4j.Category to 
org.apache.log4j.Logger should be enough to fix logging-commons, ant 
and velocity and it is the right thing to do.

Might be difficult to write a Category that doesn't break some code, so 
maybe it should be removed entirely but that would not affect the best 
course of action for the affected projects.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org