- slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 04 Feb '18

04 Feb '18

[ https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.… ] Pappy STĂNESCU commented on SLF4J-429: -------------------------------------- Your statement that using OFF for Logger.log is a misuse of JUL is rather eccentric, JUL would throw by itself an ILA if the argument is not allowed. Again, the use case is when the level is configured at runtime and when OFF is used to disable logging. The fact that SLF4J decides to log a record which is otherwise *not logged* in the absence of SLF4J is definitely wrong. But it's your call in the end, and I already spent too much time on this issue. > 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)

1 0

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 04 Feb '18

04 Feb '18

[ https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-429. ------------------------------ Resolution: 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)

1 0

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 04 Feb '18

04 Feb '18

[ https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.… ] 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)

1 0

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 04 Feb '18

04 Feb '18

[ https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü reopened SLF4J-429: ------------------------------ > 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)

1 0

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 04 Feb '18

04 Feb '18

[ https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.… ] Pappy STĂNESCU commented on SLF4J-429: -------------------------------------- Well, your own test proves the opposite, after executing the statement at line 93 in {{SLF4JBridgeHandlerTest}}, {{listAppender.list}} is of size 7... See my previous comment... > 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)

1 0

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 04 Feb '18

04 Feb '18

[ https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-429: ---------------------------------- One can indeed invoke a logger with Level.OFF. However, that invocation would not trigger any further action. In particular, *no *LogRecord with level OFF would ever reach SLF4JBridgeHandler. See also source code for java.util.Logger.log() method. > 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)

1 0

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 04 Feb '18

04 Feb '18

[ https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.… ] Pappy STĂNESCU commented on SLF4J-429: -------------------------------------- It *is* possible to log at *any* level by calling {{java.util.logging.Logger.log}}, which is what actually jersey or any other application that wants to configure the level at runtime does. See your test {{SLF4JBridgeHandlerTest.testLevels}} failing here [https://github.com/pa314159/slf4j/tree/SLF4J-429/failure] > 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)

1 0

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 04 Feb '18

04 Feb '18

[ 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)

1 0

[JIRA] (SLF4J-429) jul-to-slf4j still logs OFF level
by QOS.CH (JIRA) 03 Feb '18

03 Feb '18

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)

1 0

[JIRA] (SLF4J-428) automatic module name for jul-to-slf4j contains illegal token
by QOS.CH (JIRA) 31 Jan '18

31 Jan '18

[ https://jira.qos.ch/browse/SLF4J-428?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-428. ------------------------------ Resolution: Fixed > automatic module name for jul-to-slf4j contains illegal token > ------------------------------------------------------------- > > Key: SLF4J-428 > URL: https://jira.qos.ch/browse/SLF4J-428 > Project: SLF4J > Issue Type: Bug > Components: jul-to-slf4j > Affects Versions: 1.8.0-beta1 > Reporter: Peter-Josef Meisch > Assignee: Ceki Gülcü > Fix For: 1.8.0-beta2 > > > the automatic module name that is created in Java 9 for the jul-to-slf4 jar is _jul.to.slf4j(a)1.8.0-beta1_. This contains the token *to* which is a reserved word in Java 9 so the generated name cannot be used in requires statements in modul-info.java files of projects using jul-to-slf4j and inhibits migration of projects to Java 9. > This should be modified by adding > {{Automatic-Module-Name: jul_to_slf4j}} > to the manifest for the archive. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0