- slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-124) Add ability to log at a dynamic level
by QOS.CH (JIRA) 08 May '19

08 May '19

[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-124: ---------------------------------- Obviously, SLF4J made a distinction between levels in {{org.slf4j.Logger}} about levels via printing methods such as {{Logger.debug}} {{Logger.info}} etc. However, until relatively recently, SLF4J did not have {{Level}} defined a distinct class/enum. This will change in 2.0 which introduces the notion of a piecemeally constructed {{LoggingEvent}}. As such, it makes sense to support logging at dynamic level. > 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 > Fix For: 2.0 > > 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 (v7.3.1#73012)

1 0

[JIRA] (SLF4J-124) Add ability to log at a dynamic level
by QOS.CH (JIRA) 08 May '19

08 May '19

[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.… ] Ralph Goers commented on SLF4J-124: ----------------------------------- I am not following. The translation you are talking about would never happen in SLF4J. SLF4J can't know anything about the logging implementation such as how to translate levels. It would happen in the binding between SLF4J and the implementation. In Log4j 2's case, I would simply modify log4j-slf4j-impl's Log4jLogger to map SLF4J log Levels to the Levels that the Log4j API uses, which is exactly what Log4j does for JUL. It really is not a big deal. I guess it might impact Logback the most since it uses SLF4J directly as its API, but I would expect SLF4J would simply inherit Logback's Level definitions. > 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 (v7.3.1#73012)

1 0

[JIRA] (SLF4J-124) Add ability to log at a dynamic level
by QOS.CH (JIRA) 08 May '19

08 May '19

[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.… ] Joachim Durchholz commented on SLF4J-124: ----------------------------------------- The big deal is that SLF4J would have to make sure that it is properly translating the levels to that backend's idea of log levels. This isn't always trivial. Also, people will expect numeric log levels to be passed through unchanged. (Oracle's JDBC is truly bizarre here: it does not differentiate between DEBUG and TRACE, it simply uses one or two dozen numeric log levels across the entire DEBUG and TRACE range defined by java.util.logging. Mapping this to non-numeric libraries like logback will not be possible, to Logback may get pressured into having a numeric log level anyway.) Re whether numeric log levels are an ugly hack: Yes, but it's the least common denominator between all logging backends, and DEBUG vs. TRACE isn't granular enough for Oracle's log levels, and with JDBC, does even make sense because the more verbose log levels can generate huge amounts of trace, so if SLF4J could support the difference between 50000 and 40000 it would be helpful for ojdbc user. (I know this is just supporting and perpetuating bad architectur. But Oracle isn't going to improve this, ever, that company is driven purely be paying customer requests and doesn't care about architecture unless it hurts themselves.) > 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 (v7.3.1#73012)

1 0

[JIRA] (SLF4J-124) Add ability to log at a dynamic level
by QOS.CH (JIRA) 08 May '19

08 May '19

[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.… ] Ralph Goers commented on SLF4J-124: ----------------------------------- I am not sure what the big deal is here with implementing this. The Log4j 2 API has supported this since 2013. So we would have no trouble adding support for the new methods required for this, unless they do something truly bizarre. I suppose another way to solve this is for user's to use the Log4j 2 API and then use log4j-to-slf4j to route back to SLF4J. > 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 (v7.3.1#73012)

1 0

[JIRA] (SLF4J-124) Add ability to log at a dynamic level
by QOS.CH (JIRA) 07 May '19

07 May '19

[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.… ] Dan Lipofsky commented on SLF4J-124: ------------------------------------ This is the 2nd most voted for issue (technically 3rd but the first 2 are really duplicates) and it seems it would be easy to implement. Pretty please? > 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 (v7.3.1#73012)

1 0

[qos-ch/slf4j] d9690a: fix notification adress
by Ceki Gulcu 05 May '19

05 May '19

Branch: refs/heads/2.0 Home: https://github.com/qos-ch/slf4j Commit: d9690a131ecd335fdaa1e19848fe79198e5d03c4 https://github.com/qos-ch/slf4j/commit/d9690a131ecd335fdaa1e19848fe79198e5d… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-05-05 (Sun, 05 May 2019) Changed paths: M .travis.yml Log Message: ----------- fix notification adress

1 0

[JIRA] (SLF4J-459) MDC to return previous values
by QOS.CH (JIRA) 05 May '19

05 May '19

Claude Brisson created SLF4J-459: ------------------------------------ Summary: MDC to return previous values Key: SLF4J-459 URL: https://jira.qos.ch/browse/SLF4J-459 Project: SLF4J Issue Type: Improvement Components: Core API Affects Versions: 1.8.0-beta4 Environment: The put(key, value) method in MDC and MDCAdapter could easily return the previously stored value, or null if not found, since this value is returned by the underlying map. Plus, the change is fully backward compatible. This addition eases the implementation of stackable contexts by client applications, without the need of an additional map lookup to fetch the current MDC key value for latter restoration when the client context is popped up. Reporter: Claude Brisson Assignee: SLF4J developers list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 029eab: ongoing work
by Ceki Gulcu 02 May '19

02 May '19

Branch: refs/heads/2.0 Home: https://github.com/qos-ch/slf4j Commit: 029eab156923374c858a85ab656bddc48f2e33e5 https://github.com/qos-ch/slf4j/commit/029eab156923374c858a85ab656bddc48f2e… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-05-02 (Thu, 02 May 2019) Changed paths: A slf4j-api/src/main/java/org/slf4j/spi/LoggingEventAware.java M slf4j-api/src/main/java/org/slf4j/spi/LoggingEventBuilder.java Log Message: ----------- ongoing work

1 0

Prepared branch for slf4j 2.0
by Federico Fissore 02 May '19

02 May '19

Hi Ceki I prepared the branch for slf4j 2.0. I cannot make a PR that targets a non existing branch: can you make one? Code is available at https://github.com/ffissore/slf4j/tree/2.0.0-SNAPSHOT I've replaced occurrences of java 1.5 and 1.6 to 1.8 and I've included slf4j fluent Let me know what you think federico

3 11

[qos-ch/slf4j] 4d4ebb: initial backward compatible implementation of flue...
by Ceki Gulcu 29 Apr '19

29 Apr '19

Branch: refs/heads/2.0 Home: https://github.com/qos-ch/slf4j Commit: 4d4ebb395ed994263b848e300cd3e282db5fd795 https://github.com/qos-ch/slf4j/commit/4d4ebb395ed994263b848e300cd3e282db5f… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-04-29 (Mon, 29 Apr 2019) Changed paths: M slf4j-api/src/main/java/org/slf4j/Logger.java M slf4j-api/src/main/java/org/slf4j/event/DefaultLoggingEvent.java A slf4j-api/src/main/java/org/slf4j/event/LoggingEventAware.java M slf4j-api/src/main/java/org/slf4j/helpers/MessageFormatter.java M slf4j-api/src/main/java/org/slf4j/spi/DefaultLoggingEventBuilder.java A slf4j-jdk14/src/test/java/org/slf4j/jul/FluentApiInvocationTest.java M slf4j-jdk14/src/test/java/org/slf4j/jul/InvocationTest.java M slf4j-simple/src/test/java/org/slf4j/simple/InvocationTest.java Log Message: ----------- initial backward compatible implementation of fluent API

1 0