On 24.09.2010, at 17:04, Jacob Kjome wrote:
> Since Log4j must support JDK1.4 (actually, still 1.3, I believe), I don't see
> how we could use JDK1.5+ ThreadLocal.remove()?
I suspected something like this...I was actually surprised to see that there's
still development activity here.
What I see
Hi,
My name is Silviu Dusa and I am an architect for a rather large organization. I
am in charge with the assessment of Log4J for future development.
We perused the text found at the wiki site
(http://wiki.apache.org/logging-log4j/) but it is not clear what the direction
Log4J is going is.
Hi,
My name is Silviu Dusa and I am an architect for a rather large organization. I
am in charge with the assessment of Log4J for future development.
We perused the text found at the wiki site
(http://wiki.apache.org/logging-log4j/) but it is not clear what the direction
Log4J is going is.
The log4j 1.2 line will continue to be maintained.
Some work has gone into designing Log4j 2, but it is still in the early
stages.
I'm not very familiar with the logback library, but each logging library has
pros and cons relative to log4j.
One of the main differences between log4j some some of
I would add that Logback is not an Apache project so it would be inappropriate
for Log4j to discuss the future of Logback or what its release schedule is.
SLF4J is used by some Apache projects, which means that either Log4j or Logback
can be integrated.
Ralph
On Sep 30, 2010, at 1:04 PM, Sc
