Jason van Zyl <[EMAIL PROTECTED]> writes:
> I don't think there is really any downside in using log4j.
> It is certainly flexible enough and we can totally off load
> the job of logging to log4j where it belongs and remove
> logging code from Turbine completely which I think would
> greatly simply things.
>
> I am getting to point where trying to separate our
> various bits of functionality into components is
> a real PITA when it comes to logging. I think log4j
> would provide a clean consistent method for logging.
> The only other real competitor is the logging JSR
> which isn't complete, will require 1.4, and isn't
> as feature rich as log4j. And I really do think
> rolling our own logging system is a waste of time.
I know that Jon and the e-point folks spent a lot of time on the
Logging service, but I'm am always in favor of simplification and
narrow APIs. Jason, if you really think this is a necessary change,
you have my +1.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
