> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 18, 2003 2:59 PM
> To: [EMAIL PROTECTED]
> Subject: Apache Logging Services top level project
> 
> The proposal that Stephen pointed out last Friday was adopted.  There is a
> new logging services TLP.
> 
> I don't know if LogKit should move or not.  Perhaps a bit of both.  There
> is
> code in LogKit that I think could certainly be contributed, yes.  And
> there
> is code that should be largely an Avalon adapter to the other logging
> mechanisms.  Both are things that can be discussed.
> 
>       --- Noel

I've been meaning to write a "State of Logging in Avalon" email, but figured
I'd wait until I had time to actually do something about it before opening
my mouth.

However, for those wondering, here's the summary:

We have three logging packages:

1. Framework Logger: org.apache.avalon.framework.logger  
2. LogKit:  org.apache.log
3. Excalibur Logging: org.apache.avalon.excalibur.logger

Framework Logging is VERY similar to Jakarta commons logging both in intent
and in actual code.  The basic idea is a light weight wrapper for the
various logging libraries (1.4 logging, log4j, logkit,...).

LogKit is a full blown logging framework (think log4j) that also works as an
Avalon component.

Excalibur Logging provides a number of the facilities of Framework logging
(wrappers for loggers) but includes some other implementation details and
general utilities.  I think it is only used in Fortress (does Phoenix use
it?).

It's easy to see how users get confused from time to time about this.  My
thought is that it would be nice to contribute as much as we can to the new
TLP and in the process clean up and simplify the logging situation here.

J. Aaron Farr
  SONY ELECTRONICS
  DDP-CIM
  (724) 696-7653

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to