June 2021 - slf4j-dev - mailman3.qos.ch

[JIRA] Updates for SLF4J-490: Better combination for logging and exceptions
by QOS.CH (JIRA) 30 Jun '21

30 Jun '21

SLF4J / SLF4J-490 [Closed] Better combination for logging and exceptions ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-490 ============================== 1 comment ------------------------------ Norbert Kiesel on 30/Jun/21 11:27 PM Fair enough. My motivations came from encouraging my developers to use the `{}` approach. Too often, they use ```java logger.error(String.format("Param %s must be in "[%s-%s]", name, low, high)); ``` Thus, it would be nice to have an unified template mechanism for both logging and exceptions ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-490: Better combination for logging and exceptions
by QOS.CH (JIRA) 30 Jun '21

30 Jun '21

SLF4J / SLF4J-490 [Resolved] Better combination for logging and exceptions ============================== Here's what changed in this issue in the last few minutes. There are 2 updates, 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-490 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 30/Jun/21 9:10 PM Resolution: Not a bug Status: Resolved (was: Open) ============================== 1 comment ------------------------------ Ceki Gülcü on 30/Jun/21 9:10 PM Given that the formatted message has to be constructed independent of the logging level, I think formatting the message outside slf4j should be OK. Nevertheless, I am taking a mental note of this issue. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-474: Redirect references to pipermail archives
by QOS.CH (JIRA) 30 Jun '21

30 Jun '21

SLF4J / SLF4J-474 [Resolved] Redirect references to pipermail archives ============================== Here's what changed in this issue in the last few minutes. There are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-474 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 30/Jun/21 8:06 PM Resolution: Fixed Status: Resolved (was: Open) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-510: Release 2.x already
by QOS.CH (JIRA) 30 Jun '21

30 Jun '21

SLF4J / SLF4J-510 [Resolved] Release 2.x already ============================== Here's what changed in this issue in the last few minutes. There are 2 updates, 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-510 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 30/Jun/21 7:35 PM Resolution: Not a bug Status: Resolved (was: In Progress) ============================== 1 comment ------------------------------ Ceki Gülcü on 30/Jun/21 7:35 PM Progress on releasing 2.0.0-alpha2 is being made. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-432: log4j-over-slf4j calls wrong methods when marker parameter is null
by QOS.CH (JIRA) 30 Jun '21

30 Jun '21

SLF4J / SLF4J-432 [Resolved] log4j-over-slf4j calls wrong methods when marker parameter is null ============================== Here's what changed in this issue in the last few minutes. There are 2 updates, 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-432 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 30/Jun/21 7:26 PM Resolution: Won't Fix Status: Resolved (was: In Progress) ============================== 1 comment ------------------------------ Ceki Gülcü on 30/Jun/21 7:26 PM Users may call printing methods with a null valued Marker as well as null valued throwable. As such, I marking this issue as RESOLVED WONT FIX. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-435: Minor typo in FAQ
by QOS.CH (JIRA) 29 Jun '21

29 Jun '21

SLF4J / SLF4J-435 [Resolved] Minor typo in FAQ ============================== Here's what changed in this issue in the last few minutes. There are 2 updates. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-435 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 29/Jun/21 11:16 PM Resolution: Fixed Status: Resolved (was: In Progress) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[qos-ch/slf4j] b4b2f6: fix SLF4J-435
by Ceki Gulcu 29 Jun '21

29 Jun '21

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: b4b2f6fef7f0131be61ab352c90d4189ace96d84 https://github.com/qos-ch/slf4j/commit/b4b2f6fef7f0131be61ab352c90d4189ace9… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2021-06-29 (Tue, 29 Jun 2021) Changed paths: R slf4j-api/src/test/java/org/slf4j/LoggerUsage.java A slf4j-api/src/test/java/org/slf4j/basicTests/FluentAPIUsage.java M slf4j-site/src/site/pages/faq.html Log Message: ----------- fix SLF4J-435

1 0

[JIRA] Updates for SLF4J-124: Add ability to log at a dynamic level
by QOS.CH (JIRA) 29 Jun '21

29 Jun '21

SLF4J / SLF4J-124 [In Progress] Add ability to log at a dynamic level ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-124 ============================== 1 comment ------------------------------ Ceki Gülcü on 29/Jun/21 10:58 PM The 2.0 API introduces a new method, namely {{Logger.makeLoggingEventBuilder(Level)}} which an be used to accomplish the desired outcome. Example code: {code:java} public void logAMessageAtGivenLevel(Level aLevel, String aMessage) { Logger logger = .. // some slf4j logger of choice logger.makeLoggingEventBuilder(aLevel).log(aMessage); } {code} The default implementation will return a NOPLoggingEventBuilder if the logger is disabled for the given Level. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[qos-ch/slf4j] 49831a: add isEnabledForLevel method in Logger
by Ceki Gulcu 29 Jun '21

29 Jun '21

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 49831a3f065b8b6b310e04a6fe5e04dd10eeec12 https://github.com/qos-ch/slf4j/commit/49831a3f065b8b6b310e04a6fe5e04dd10ee… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2021-06-29 (Tue, 29 Jun 2021) Changed paths: M slf4j-api/src/main/java/org/slf4j/Logger.java M slf4j-api/src/test/java/org/slf4j/helpers/SubstitutableLoggerTest.java Log Message: ----------- add isEnabledForLevel method in Logger

1 0

[qos-ch/slf4j] 49356a: make NOPLoggingEventBuilder constructor private an...
by Ceki Gulcu 29 Jun '21

29 Jun '21

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 49356a792ac8b2c7fde6fe8429784c6e706802b2 https://github.com/qos-ch/slf4j/commit/49356a792ac8b2c7fde6fe8429784c6e7068… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2021-06-29 (Tue, 29 Jun 2021) Changed paths: M slf4j-api/src/main/java/org/slf4j/spi/NOPLoggingEventBuilder.java Log Message: ----------- make NOPLoggingEventBuilder constructor private and allow access via the singleton

1 0