> -----Original Message----- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: Friday, March 05, 2004 9:35 AM > To: 'Avalon Developers List' > Subject: Logging at Avalon > > Hi, > > I'm still trying to find out what the different logging projects > here are trying to do and what the general direction is? > > So far I found out: there is: > - LogKit > - Interfaces in Avalon Framework api > - Implementations in Avalon Framework impl > - API and impl in Excalibur Logger > - API and impl in Avalon Logging > > Can anyone please explain what the different projects do and what > is planned for them in the near future?
http://marc.theaimsgroup.com/?l=avalon-dev&m=107743895212992&w=2 Stephen put that together recently. I think it will answer most of your questions. 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. 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. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
