pglezen 01/05/30 22:23:26
Modified:src/java/org/apache/log4j PropertyConfigurator.java
Log:
1. Change accessibility of configureCategoryFactory from package to protected.
2. Fixed a javadoc link to the Filter class.
Revision ChangesPath
1.24 +2 -2
jakarta-lo
Anders,
Not to quibble but the result was actually 4 committers +1 and 3 users +1 which does
not alter the final outcome of the vote. Formally, only committer votes count. The
committer privilege also grants veto rights.
In any case, welcome Jim! Regards, Ceki
At 14:04 30.05.2001 -0400, you
Thanks to everyone for casting their votes. The result was 7 to 0 in
favor of making Jim a committer and so I've asked the appropriate
authorities (Brian Behlendorf) to add an account for Jim.
Anders
Anders Kristensen wrote:
>
> Hi,
>
> I'd like to propose that Jim is given committer privileg
I'm not sure I agree that creating the directory that the use specifies is
doing something "behind the user's back" any more than log4j creating the
log file itself is. The user's saying "I want the file here," so creating
the file there (directory and filename) is doing exactly what the user ask
Elisabeth,
It is the user's responsibility to make sure that the destination file is writable.
log4j avoids doing things behind the user's back. If the directory does not exists
then logging fails for the relevant appender. Regards, Ceki
At 15:20 30.05.2001 +0200, you wrote:
>Hello,
>
>I have
Hello,
I have a problem concerning the creation of output files.
Apparently, if the directory of the output file specified in the
configuration file does not exist, log4j does not create it but throws
an Exception.
As it would be useful in our project to have these directories created
automatic
