Hello,
Simon Kitching wrote:
If I were writing a 1.4+ library or app, I'd just use java.util.logging
directly.
Which reminds me: is the JULI implementation of the java.util.logging
API (used in tomcat) available as an independent library? If not, maybe
it is worth extracting it as a project of
On 31/07/06, Henri Yandell [EMAIL PROTECTED] wrote:
On 7/28/06, James Carman [EMAIL PROTECTED] wrote:
...
Sure you could argue that log4j is more powerful, but the same could
be said of ORO. Increasingly people just aren't going to care. We're
starting to talk about moving to 1.3 so we can
On 7/28/06, James Carman [EMAIL PROTECTED] wrote:
Tapestry is thinking of switching to SL4J instead of Jakarta Commons
Logging:
I've been meaning to ask... is there really much reason for a JDK 1.4+
application/library to depend on commons-logging?
Sure you could argue that log4j is more
On Mon, 2006-07-31 at 13:08 -0700, Henri Yandell wrote:
On 7/28/06, James Carman [EMAIL PROTECTED] wrote:
Tapestry is thinking of switching to SL4J instead of Jakarta Commons
Logging:
I've been meaning to ask... is there really much reason for a JDK 1.4+
application/library to depend on
Curdt
Sent: Saturday, July 29, 2006 12:10 AM
To: Jakarta Commons Developers List
Subject: Re: [logging] Tapestry and JCL
A pretty common complaint is that commons-logging is a problem. It does
some wierd and awkward class loading things that ultimately result in
memory
leaks.
Well, it's probably
: [logging] Tapestry and JCL
From: James Carman [EMAIL PROTECTED]
Thoughts?
I would really hate to see an
Apache TLP, java-based project switch off JCL in favor of a non-ASF
logging API.
Unless I'm mistaken, SLF4J comes from Ceki, creator of Log4J. Thus the SLF4J
website and separation
From: James Carman [EMAIL PROTECTED]
Thoughts?
I would really hate to see an
Apache TLP, java-based project switch off JCL in favor of a non-ASF
logging API.
Unless I'm mistaken, SLF4J comes from Ceki, creator of Log4J. Thus the SLF4J
website and separation is as much for political reasons
AM
To: Jakarta Commons Developers List
Subject: Re: [logging] Tapestry and JCL
From: James Carman [EMAIL PROTECTED]
Thoughts?
I would really hate to see an
Apache TLP, java-based project switch off JCL in favor of a non-ASF
logging API.
Unless I'm mistaken, SLF4J comes from Ceki, creator
A pretty common complaint is that commons-logging is a problem. It does
some wierd and awkward class loading things that ultimately result in memory
leaks.
Well, it's probably not me to answer (Simon?) but AFAIU most of these
things were addressed with the last release of JCL. What's left is
