Torsten Curdt wrote:
There are two variations on loglit configuration - one in excalibur and one in avalon/logging. See the following email for details:
http://marc.theaimsgroup.com/?l=avalon-dev&m=107743895212992&w=2
Thanks for the pointer, Steven :)
you are talking about "end-of-life" and "exists for legacy reasons"
...would you rather see people using a different logger package for future projects?
My personal position ?
... yes.
I think that as far as the container-side logging service api is concerned - the avalon-logging package is looking good (just a couple of tweaks needed on the API before its a release candidate). The main thing missing is to provide a nice integration of a Log4J plugin, then switch from LogKit to Log4J as the default logging implementation. We can then send LogKit off to Florida with a one way ticket and shortly after Excalibur Logging.
Stephen.
cheers -- Torsten
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
