I hope.
http://cvs.apache.org/builds/logging/log4j/log4j-1.2.12
For some reason all of the .class files are different than the 1.2.12rc6
build. I don't know why. I verified that jdk 1.3.1_16 was used to do the
build.
Curt, can you run this version through the battery of tests in your
envi
mwomack 2005/08/29 22:26:03
Modified:docs Tag: v1_2-branch HISTORY.txt
Log:
Updating date for 1.2.12 release.
Revision ChangesPath
No revision
No revision
1.27.2.23 +1 -1 logging-log4j/docs/HISTORY.txt
Index: HISTORY.t
Excellent.
On 8/29/05, Ceki Gülcü <[EMAIL PROTECTED]> wrote:
>
> Dan.
>
> Are you aware of SLF4J API which already incorporates a similar approach?
>
> See for example the Logger class:
>
>http://www.slf4j.org/api/org/slf4j/Logger.html
>
> At 09:14 PM 8/29/2005, Dan Bush wrote:
> [cut]
>
Dan.
Are you aware of SLF4J API which already incorporates a similar approach?
See for example the Logger class:
http://www.slf4j.org/api/org/slf4j/Logger.html
At 09:14 PM 8/29/2005, Dan Bush wrote:
[cut]
USAGE 2: (SUGGESTED EXTENDED API)
logger.debug("ci:[{0
I have been recompiling log4j locally for years now to overload the
logging signature so I can take advantage of java.text.MessageFormat
and embed the isXXXEnabled check. Below I have detailed out what I am
doing but, I would like to know if it is something that could be
incorporated into the frame
