I have been watching the Turbine dev thread, and it seems that this same thing has happened in T2.3 dev.. Henning removed all the Turbine Logging stuff in favor of log4j... Just something to look at.
Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 12:05 PM To: [EMAIL PROTECTED] Subject: DO NOT REPLY [Bug 15214] - Cleanup Logging DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15214>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15214 Cleanup Logging ------- Additional Comments From [EMAIL PROTECTED] 2002-12-23 17:04 ------- I think that step one to achieve what Raphael is proposing is to provide a replacement for Turbine Logging Service. This service makes it difficult to configure log4j loggers and its properties are confusing to say the least. I propose implementing our own logging service based on commons logging. We would continue using Turbine Log wrapper so no global coding change would be required. Since log4j is the default framework for commons logging, we would provide a default log4j.properties file and allow the users to fine tune logging to their liking. Any comments? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
