[logback-dev] [Bug 73] New: LOGBack 0.9.5 doesn't work with SLF4J 1.4.0
bugzilla-daemon at pixie.qos.ch
bugzilla-daemon at pixie.qos.ch
Wed May 23 00:27:07 CEST 2007
http://bugzilla.qos.ch/show_bug.cgi?id=73
Summary: LOGBack 0.9.5 doesn't work with SLF4J 1.4.0
Product: logback-core
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: blocker
Priority: P1
Component: Other
AssignedTo: logback-dev at qos.ch
ReportedBy: agerwe at acxiom.com
With the addition of the trace level in SLF4J 1.4.0, the constants for the log
level constants in org.slf4j.spi.LocationAwareLogger were changed from 0, 1, 2,
3 to 10, 20, 30, 40.
Unfortuantely, constant values like integers are actually compiled into classes
and not read at runtime from the defining class: you need to upgrade all your
binaries if you change the values of constants. The case statement at line 745
in ch.qos.logback.classic.Logger no longer works unless manually recompiled
against the new Log4j. If you try to use LOGBack-classic 0.9.5 from iBiblio
with SLF4J 1.4.0 (which seems to be missing :-(), you will not be able to log
anything: every non-TRACE log attempt will fail with "n is not a valid integet"
[sic] where n is 10, 20, 30 or 40.
It would have been *much* wiser to simply set TRACE to -1 or even 4 rather than
changing the existing constants and creating a big headache and forced binary
upgrades that are very difficult to debug.
--
Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the logback-dev
mailing list