[ 
https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19116#comment-19116
 ] 

Ceki Gülcü commented on SLF4J-429:
----------------------------------

Yes, I see the problem. My assertion that logging at Level.OFF would not any 
trigger action is wrong. The converse is true. Logging at Level.OFF will always 
trigger logging (unless the logger's level was set to true). 

Logging at Level.OFF is a misuse of the jul logging system. In any case, 
SLF4JBridgeHandlerTest current behavior is quite reasonable. Changing 
resolution to NOT_A_BUG.

> jul-to-slf4j still logs OFF level
> ---------------------------------
>
>                 Key: SLF4J-429
>                 URL: https://jira.qos.ch/browse/SLF4J-429
>             Project: SLF4J
>          Issue Type: Bug
>          Components: jul-to-slf4j
>    Affects Versions: 1.7.25
>            Reporter: Pappy STĂNESCU
>            Assignee: Ceki Gülcü
>              Labels: logging
>
> SLF4JBridgeHandler maps java.util.logging.Level.OFF to 
> LocationAwareLogger.ERROR_INT.
> This causes logging that has been turned off to still be logged at the ERROR 
> level.
> See this bug at work at https://github.com/jersey/jersey/issues/3527



--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
slf4j-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-dev

Reply via email to