LocationInfo is allowed to fail in extracting caller information while
Logger.getLogger(...) must always succeed. If LocationInfo fails you
either get incorrect location information or just '?' for the %M, %C,
%L, %F pattern converters. If Logger.getLogger() fails then the whole
named hierarchy bec
Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Mon 12/20/2004 10:21 AM
To: Log4J Developers List
Cc:
Subject: RE: cvs commit: logging-log4j/src/java/org/apache/log4j
LogManager.java
Hello,
Indeed, testing the automatic logger naming feature will be quite hard
to test on all
Hello,
Indeed, testing the automatic logger naming feature will be quite hard
to test on all platforms. Not only that, the behavior of a particular
JVM may vary between the test environment and the environment of a
real-world application. So no amount of brute-force (automated)
testing
;m just explaining why I made the commit.
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Mon 12/20/2004 3:09 AM
To: Log4J Developers List
Cc:
Subject: Re: cvs commit: logging-log4j/src/java/org/apache/log4j
LogManager.java
Scott,
Please see http://marc.the
Scott,
Please see http://marc.theaimsgroup.com/?t=11015036401&r=1&w=2
Log4, as the most popular a logging API, must be reliable. Speed,
convenience, user demand are all secondary considerations when
compared with reliably. This change severely compromises
reliability. It must be either backed u
Quoting Ceki Gülcü <[EMAIL PROTECTED]>:
>
> Jake,
>
> I am -1 about this change.
I'm sorry to hear that. Log4j should not make it possible to bring down the
entire appserver based on one developer's initialization code, period, end of
story.
Jake
>
> Custom initialization scripts for setting
Jake,
I am -1 about this change.
Custom initialization scripts for setting a repository selector should use
the following template:
// set the selector to MyRepositorySelector, preserving the
// existing default repository. However, if MyRepositorySelector has its
// own special defaultRepository
