On Sat, 2002-06-15 at 17:12, Berin Loritsch wrote: > I find the logger package to be pretty decent. However, there are a few > things > to consider: > > 1) Instead of having many different logging abstractions, what about > using > Commons Logging (ducks and hides)?
+0. Would be cool but what we have is extremely stable so I have no *need* to change. Also, dependency would be like this Avalon LogKit <--loose-- commons logging <-- Avalon Framework Which is cool, just something to keep in mind. > 2) If we maintain our own, what about a "TRACE" logging level. It is > useful > debugging information that is not necessary for all debugging > excercises. > Some bugs are only found by tracing through, so a message when > entering > a method or exiting a method can be helpful. Esp. if your Java > debugger > is effectively broken (happens more often than I care to mention). eh? You mean you want to put trace() statements in your code for the lack of a good debugger? -1. Get a good debugger, I'd say. Tracing is a separate concern from logging. - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
