Reason why Excalibur Logging package won't work:

[Berin Loritsch <bl...@infoplanning.com>]

In addition to many performance improvements, bug fixes, and other small 
enhancements, log4j 1.2 adds JMX support, Mapped Diagnostic Contexts, 
JDBC logging, graphical log viewer (chainsaw), and buffered IO 
capability. One important change is the replacement of the |Category| 
class with |Logger| class and the |Priority| class with the |Level| 
class in order to facilitate migrating from the JDK 1.4 logging API to 
log4j.


We either need to support Log4J 1.2+, or Log4J 1.1.x



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Reason why Excalibur Logging package won't work:

[Peter Donald <pe...@apache.org>]

On Wed, 9 Oct 2002 23:29, Berin Loritsch wrote:
> In addition to many performance improvements, bug fixes, and other small
> enhancements, log4j 1.2 adds JMX support, Mapped Diagnostic Contexts,
> JDBC logging, graphical log viewer (chainsaw), and buffered IO
> capability. One important change is the replacement of the |Category|
> class with |Logger| class and the |Priority| class with the |Level|
> class in order to facilitate migrating from the JDK 1.4 logging API to
> log4j.
>
>
> We either need to support Log4J 1.2+, or Log4J 1.1.x

Can we have a Log4j2LogManager that does 1.2+ and Log4jLogManager that does 
1.1 ? That way we deprecate/kill 1.1 version. Alternatively we could just 
kill 1.1 support.

-- 
Cheers,

Peter Donald
---------------------------------------------------
"It is easy to dodge our responsibilities, but we 
cannot dodge the consequences of dodging our 
responsibilities." -Josiah Stamp 
--------------------------------------------------- 



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>