[ https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.… ]
Ceki Gülcü resolved SLF4J-429.
------------------------------
Resolution: Cannot Reproduce
It is not possible to log at the OFF level. So the "mapping" of the OFF level does not matter. Please create a unit test illustrating the problem. In the mean time, I am closing this issue as CANNOT REPRODUCE.
> 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: SLF4J developers list
> 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)
Răzvan STĂNESCU created SLF4J-429:
-------------------------------------
Summary: 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: Răzvan STĂNESCU
Assignee: SLF4J developers list
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)
