slf4j-dev

Download

slf4j-dev@qos.ch

February 2017

4 participants
72 discussions

[JIRA] (SLF4J-393) Fix MDC issue with slf4j-log4j12
by QOS.CH (JIRA) 14 Feb '17

14 Feb '17

Ceki Gülcü created SLF4J-393: -------------------------------- Summary: Fix MDC issue with slf4j-log4j12 Key: SLF4J-393 URL: https://jira.qos.ch/browse/SLF4J-393 Project: SLF4J Issue Type: Sub-task Components: Implementations Affects Versions: 1.7.22 Environment: Incorrect parsing of the java.version system property in log4j 1.2 disables MDC. Enable log4j's MDC by reflection. Reporter: Ceki Gülcü Assignee: Ceki Gülcü Fix For: 1.7.23 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-392) Comment on level ordering in the Logger javadoc
by QOS.CH (JIRA) 08 Feb '17

08 Feb '17

Jason Sachs created SLF4J-392: --------------------------------- Summary: Comment on level ordering in the Logger javadoc Key: SLF4J-392 URL: https://jira.qos.ch/browse/SLF4J-392 Project: SLF4J Issue Type: Improvement Components: Core API Affects Versions: 1.7.22 Reporter: Jason Sachs Assignee: SLF4J developers list Priority: Minor This may be a stupid question, but the {{Logger [javadocs|https://www.slf4j.org/api/org/slf4j/Logger.html] merely say that }} ---- {{*[debug|https://www.slf4j.org/api/org/slf4j/Logger.html#debug(org.slf4j.Marker, java.lang.String)]*([Marker|https://www.slf4j.org/api/org/slf4j/Marker.html] marker, [String|http://java.sun.com/j2se/1.5.0/docs/api/java/lang/String.html?is-ext…] msg)}} Log a message with the specific Marker at the DEBUG level. {{*[error|https://www.slf4j.org/api/org/slf4j/Logger.html#error(org.slf4j.Marker, java.lang.String)]*([Marker|https://www.slf4j.org/api/org/slf4j/Marker.html] marker, [String|http://java.sun.com/j2se/1.5.0/docs/api/java/lang/String.html?is-ext…] msg)}} Log a message with the specific Marker at the ERROR level. {{*[info|https://www.slf4j.org/api/org/slf4j/Logger.html#info(org.slf4j.Marker, java.lang.String)]*([Marker|https://www.slf4j.org/api/org/slf4j/Marker.html] marker, [String|http://java.sun.com/j2se/1.5.0/docs/api/java/lang/String.html?is-ext…] msg)}} Log a message with the specific Marker at the INFO level. {{*[trace|https://www.slf4j.org/api/org/slf4j/Logger.html#trace(org.slf4j.Marker, java.lang.String)]*([Marker|https://www.slf4j.org/api/org/slf4j/Marker.html] marker, [String|http://java.sun.com/j2se/1.5.0/docs/api/java/lang/String.html?is-ext…] msg)}} Log a message with the specific Marker at the TRACE level. {{*[warn|https://www.slf4j.org/api/org/slf4j/Logger.html#warn(org.slf4j.Marker, java.lang.String)]*([Marker|https://www.slf4j.org/api/org/slf4j/Marker.html] marker, [String|http://java.sun.com/j2se/1.5.0/docs/api/java/lang/String.html?is-ext…] msg)}} Log a message with the specific Marker at the WARN level. ---- with no guidance on the relative levels of DEBUG, ERROR, INFO, TRACE, WARN. I presume that SLF4J merely passes these along to a supported framework, which must include at least these levels, and it is up to the framework to dictate the relative ordering? Or do you assume that all frameworks treat ERROR > WARN > INFO > DEBUG > TRACE ? Either way, it would be helpful to include at least one sentence stating this, or referring to the FAQ where the issue can be mentioned, similar to https://www.slf4j.org/faq.html#trace -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0