Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-436

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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.26
    • Component/s: logback-classic
    • Labels:
      None

      Description

      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;

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

        Attachments

          Activity

            People

            • Assignee:
              ceki Ceki Gülcü
              Reporter:
              christian Christian Brensing
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: