[logback-dev] [JIRA] Created: (LBCLASSIC-226) Add mapping for Classic-Level OFF to the corresponding JUL-Level in ch.qos.logback.classic.jul.JULHelper

[Christian Brensing (JIRA)]

Add mapping for Classic-Level OFF to the corresponding JUL-Level in ch.qos.logback.classic.jul.JULHelper
--------------------------------------------------------------------------------------------------------

                 Key: LBCLASSIC-226
                 URL: http://jira.qos.ch/browse/LBCLASSIC-226
             Project: logback-classic
          Issue Type: Bug
          Components: Other
            Reporter: Christian Brensing
            Assignee: Logback dev list


If I use the new LevelChangePropagator (since 0.9.25) with a LOGBack-Level set to OFF, an IllegalArgumentException will be thrown by ch.qos.logback.classic.jul.JULHelper.asJULLevel(Level lbLevel), which causes my RCP application to crash on startup. As the OFF-Level is supported by both LOGBack and JUL, please add a corresponding mapping in that method.

case Level.OFF_INT:
        return java.util.logging.Level.OFF;

(i) My current workaround is to completely rewrite the LevelChangePropagator class in a LOGBack-Groovy-Configuration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira