- slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-389) SimpleLogger caches System.err and System.out
by QOS.CH (JIRA) 14 Feb '17

14 Feb '17

[ https://jira.qos.ch/browse/SLF4J-389?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-389. ------------------------------ Resolution: Fixed > SimpleLogger caches System.err and System.out > --------------------------------------------- > > Key: SLF4J-389 > URL: https://jira.qos.ch/browse/SLF4J-389 > Project: SLF4J > Issue Type: Bug > Affects Versions: 1.7.x > Reporter: Igor Polevoy > Assignee: Ceki Gülcü > Fix For: 1.7.23 > > > We usually use SimpleLogger in tests, and some other binding when running in production. > In some cases, our tests depend on log values logged through the logger during a test. > Unfortunately between version 1.7.0 and 1.7.1 this ability has been removed, since the SimpleLogger now caches the system stream in a static initialiser. > Here is the code that broke this approach: > https://github.com/qos-ch/slf4j/commit/996ccc7ca507994465c069554954ecb01890… > Basically, we would write a test: > {quote}PrintStream err = System.err; > PrintStream temp = new PrintStream(some buffer here); > System.err = temp; > // run tests > System.err = err; > // here we assert that the temp stream contains values we expect{quote} > Unfortunately SimpleLogger now caches the system stream and never releases it, meaning swapping the streams to catch the output is not possible. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 983b04: minor edits
by Ceki Gulcu 14 Feb '17

14 Feb '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 983b04b546935bda09f3619c9435191e19757482 https://github.com/qos-ch/slf4j/commit/983b04b546935bda09f3619c9435191e1975… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-02-14 (Tue, 14 Feb 2017) Changed paths: M slf4j-site/src/site/pages/news.html Log Message: ----------- minor edits

1 0

[qos-ch/slf4j] 2651ad: slf4j is on Java 5
by Ceki Gulcu 14 Feb '17

14 Feb '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 2651ad2a386cad909fe3e1ee2dc52558b552fba8 https://github.com/qos-ch/slf4j/commit/2651ad2a386cad909fe3e1ee2dc52558b552… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-02-14 (Tue, 14 Feb 2017) Changed paths: M pom.xml Log Message: ----------- slf4j is on Java 5

1 0

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

14 Feb '17

[ https://jira.qos.ch/browse/SLF4J-393?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-393. ------------------------------ Resolution: Fixed Fixed in commit [01e56add155e72|https://github.com/qos-ch/slf4j/commit/01e56add155e723640] > 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

[qos-ch/slf4j] 01e56a: fix SLF4J-393
by Ceki Gulcu 14 Feb '17

14 Feb '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 01e56add155e723640a1c75ba917615317b2e73f https://github.com/qos-ch/slf4j/commit/01e56add155e723640a1c75ba917615317b2… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-02-14 (Tue, 14 Feb 2017) Changed paths: M integration/pom.xml M integration/src/test/java/org/slf4j/test_osgi/BundleTest.java M integration/src/test/java/org/slf4j/test_osgi/FelixHost.java M pom.xml M slf4j-api/src/main/java/org/slf4j/helpers/Util.java A slf4j-api/src/test/java/org/slf4j/helpers/UtilVersionTest.java A slf4j-log4j12/src/main/java/org/apache/log4j/MDCFriend.java M slf4j-log4j12/src/main/java/org/slf4j/impl/Log4jLoggerFactory.java M slf4j-log4j12/src/main/java/org/slf4j/impl/Log4jMDCAdapter.java M slf4j-log4j12/src/main/java/org/slf4j/impl/StaticMDCBinder.java A slf4j-log4j12/src/test/java/org/apache/log4j/MDCFriendTest.java M slf4j-log4j12/src/test/java/org/slf4j/InvocationTest.java M slf4j-site/src/site/pages/news.html Log Message: ----------- fix SLF4J-393

1 0

[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

[qos-ch/slf4j] 7ef791: correct bugzilla links
by Ceki Gulcu 27 Jan '17

27 Jan '17

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 7ef791c4ae9c0865c5cdc650f68f56bd7cacd4ef https://github.com/qos-ch/slf4j/commit/7ef791c4ae9c0865c5cdc650f68f56bd7cac… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-01-27 (Fri, 27 Jan 2017) Changed paths: M slf4j-site/src/site/pages/news.html Log Message: ----------- correct bugzilla links

1 0

[JIRA] (SLF4J-124) Add ability to log at a dynamic level
by QOS.CH (JIRA) 23 Jan '17

23 Jan '17

[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.… ] Anders Kreinøe commented on SLF4J-124: -------------------------------------- I am here, because I ran into this problem, and did not want to implement a custom workarround if the problem could be fixed upstream. Just because the issue has been arround for a long time, does not mean that its not still a problem for people. If java 8 requirement is just arround the corner then fine, but if its not, then lests fix this, instead of incresing the open time to 9 years. > Add ability to log at a dynamic level > ------------------------------------- > > Key: SLF4J-124 > URL: https://jira.qos.ch/browse/SLF4J-124 > Project: SLF4J > Issue Type: Sub-task > Components: Core API > Affects Versions: 1.5.x > Environment: Operating System: All > Platform: All > URL: http://stackoverflow.com/questions/2621701/setting-log-level-of-message-at-… > Reporter: Robert Elliot > Assignee: SLF4J developers list > Attachments: Util.java.patch > > > It is occasionally useful to have a log method that takes a level as a parameter. The necessary methods can be added to the Util class without any compatibility issues as far as I can see - see attached patch. -- This message was sent by Atlassian JIRA (v6.4.12#64027)

1 0

[JIRA] (SLF4J-124) Add ability to log at a dynamic level
by QOS.CH (JIRA) 23 Jan '17

23 Jan '17

[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.… ] Joern Huxhorn commented on SLF4J-124: ------------------------------------- I didn't mean to say we should go for Java 8 right now. I'd argue to hold off implementing this until we can safely go for Java 8. Given that this has been an open issue for 8 years and that everyone in need of this feature has already implemented a custom wrapper anyway I see no need for urgency. > Add ability to log at a dynamic level > ------------------------------------- > > Key: SLF4J-124 > URL: https://jira.qos.ch/browse/SLF4J-124 > Project: SLF4J > Issue Type: Sub-task > Components: Core API > Affects Versions: 1.5.x > Environment: Operating System: All > Platform: All > URL: http://stackoverflow.com/questions/2621701/setting-log-level-of-message-at-… > Reporter: Robert Elliot > Assignee: SLF4J developers list > Attachments: Util.java.patch > > > It is occasionally useful to have a log method that takes a level as a parameter. The necessary methods can be added to the Util class without any compatibility issues as far as I can see - see attached patch. -- This message was sent by Atlassian JIRA (v6.4.12#64027)

1 0