Hm. That makes sense.
Thanks.
Tom
Quoting Ceki Gülcü <[EMAIL PROTECTED]>:
>
> You have to activate internal debugging from the command line or equivalent
> by setting the log4j.debug system property. In that case, the file in use
> is output by log4j.
>
> If you enable internal debugging f
AFAIK it does not tell what file it used if you activate
log4j.debug=true.
On Sat, 21 Jun 2003 19:56:20 +0200, Ceki Gülcü wrote:
>
>I think log4j already does what you are asking for, no?
>
>At 07:26 PM 6/21/2003 +0200, you wrote:
>>A. It seems I have to start wrestling with sourcecode again
A. It seems I have to start wrestling with sourcecode again. :-)
But to answer your questions: tell / log what you know. If log4j uses
default init and found a properties file, then you can tell a
filename, if it used an inputerstream, well, then you can't.
Tom
On Sat, 21 Jun 2003 11:40:00
Hello developers,
May I suggest a very simple addition? Either provide a function or
have log4j log (log4j.debug=true) the absolute paths of the
configuration files it has found.
Currently I have libraries that have log4j configuration files in
their JARs and of course the project itself has one.
