No need to report a bug, since it isn't one. Try doing...
This should work if one builds from the latest Log4j source.
Jake
Quoting Mark Womack <[EMAIL PROTECTED]>:
> So noted. Would anyone be interested in logging a bug?
>
> Also, we are in the process of determining th
So noted. Would anyone be interested in logging a bug?
Also, we are in the process of determining the release schedule for v1.3
going forward. Nothing is solid yet, but we are looking at a release of
v1.3 before the end of the year, with a beta release around late summer.
-Mark
> -Original
I've read on this list that this output is turn off in CVS already.
Gary
-Original Message-
From: Juan Jose Garcia Lau [mailto:[EMAIL PROTECTED]
Sent: Monday, May 09, 2005 1:57 PM
To: Log4J Users List
Subject: RE: log4j 1.3 update needed...
Best regards developers:
I agree with Hein, i
Best regards developers:
I agree with Hein, in the next release, please make an option to turn
off the log4j internal output log.
Thanks,
Juan
-Original Message-
From: Hein Meling [mailto:[EMAIL PROTECTED]
Sent: Domingo, 08 de Mayo de 2005 03:12 p.m.
To: log4j-user@logging.apache.org
Hein,
I am not a log4j developer, just a log4j user. But I understand
development quite well. We would all like easy to build, friendly CVS,
alpha and beta vesions, but those are not part of the product. Alpha
versions of any software are expected to be a mess... the whole purpose
of their exis
