> I think the general idea is to move the good stuff from excalibur-logging
> over to avalon-logging, thus integrating it better into the core framework
> and eventually dropping Excalibur logging (I think it should have been in
> framework to begin with myself).  My only concern here is that these
> logging
> packages are very close to Jakarta commons-logging and I'd like to see
> interoperability there and less re-inventing the wheel.

+1 with all points

> Logkit is a complete logging solution but it's not necessarily any better
> or
> worse than log4j.  There are some thoughts of removing it in favor log4j
> or
> perhaps donating it to the logging @ apache people.  Point is, there's no
> need to have strong dependencies between Avalon code and LogKit.  The
> containers and components should be log framework neutral.

+1

Alex



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

Reply via email to