Not yet. Probably should go into 2.0 alpha, but we need to think about
the issues in my last two posts. Once I get 1.2 beta out the door, I'll
take the time to patch this into 2.0. Want to talk things out with you
all (specifically you and Andrew) before we finalize our logging
architecture.
The attached patch modifies the logging scheme to use the jakarta commons
logging package.
I was originally planning to cache the logger once for each class or once
for each instance. Then I realized that this might make dynamically
changing the logging level, etc. at run time difficult, since co
uesday, December 03, 2002 8:16 PM
To: [EMAIL PROTECTED]
Subject: Re: Internal logging API
Daniel Rall wrote:
Ryan, I've been wanting more elegant handling logging since I started
working with the package. Rather than make a little tweak here and a
little tweak there, I think it's
() as a deprecated
method that configures the logging package to print messages on System.out.
--Ed Tellman
-Original Message-
From: Ryan Hoegg [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 8:16 PM
To: [EMAIL PROTECTED]
Subject: Re: Internal logging API
Daniel Rall wrote:
>
Daniel Rall wrote:
Ryan, I've been wanting more elegant handling logging since I started
working with the package. Rather than make a little tweak here and a
little tweak there, I think it's time for a more whole-sale approach.
What's the minimum number of class we'd have to include to make use
