- slf4j-dev - mailman3.qos.ch

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

23 Aug '22

SLF4J / SLF4J-124 [Resolved] Add ability to log at a dynamic level ============================== 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-124 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 23/Aug/22 10:35 PM Resolution: Fixed Status: Resolved (was: In Progress) ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-555: Binders are deprecated in SLF4J 2
by QOS.CH (JIRA) 23 Aug '22

23 Aug '22

SLF4J / SLF4J-555 [Resolved] Binders are deprecated in SLF4J 2 ============================== 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-555 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 23/Aug/22 10:43 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-555: Binders are deprecated in SLF4J 2
by QOS.CH (JIRA) 23 Aug '22

23 Aug '22

SLF4J / SLF4J-555 [Open] Binders are deprecated in SLF4J 2 ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-555 ============================== Issue created ------------------------------ Witalij Berdinskich created this issue on 23/Aug/22 9:52 PM Summary: Binders are deprecated in SLF4J 2 Issue Type: Bug Assignee: SLF4J developers list Components: Core API Created: 23/Aug/22 9:52 PM Environment: Version 2.0.0 is not in the list Priority: Minor Reporter: Witalij Berdinskich Description: FAQ says, see [What has changed in SLF4J version 2.0.0?|https://www.slf4j.org/faq.html#changesInVersion200] {quote}SLF4J 1.7.x and earlier versions relied on the static binder mechanism which is no loger honored by slf4j-api version 2.0.x. {quote} The static binder classes were removed in [remove org.slf4j.impl package - fixes SLF4J-407|https://github.com/qos-ch/slf4j/commit/6ac20c6a0ae96ea6609f24d92e…] But *Binder interfaces are not removed and not deprecated. PR https://github.com/qos-ch/slf4j/pull/299 ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

Release of SLF4J version 2.0.0
by Ceki Gülcü 20 Aug '22

20 Aug '22

Hello all, After a very long gestation period, I am pleased to announce SLF4J 2.0.0. The 2.0.x series introduces a backward-compatible fluent logging API. By backward-compatible, we mean that existing logging frameworks do not have to be changed in order for the user to benefit from the fluent logging API. However, existing frameworks *must* migrate to the ServiceLoader mechanism. The resulting internal changes are detailed in the FAQ page. http://www.slf4j.org/faq.html#changesInVersion200 The 2.0.x series builds upon the the 1.8.x series which was modularized per Java Platform Module System (JPMS/Jigsaw). The 2.0.x series requires Java 8. Please refer to the the news page for more details on this release: http://www.slf4j.org/news.html Binary compatibility: Mixing mixing different versions of slf4j-api.jar and SLF4J provider can cause problems. For example, if you are using slf4j-api-2.0.0.jar, then you should also use slf4j-simple-2.0.0.jar, using slf4j-simple-1.5.5.jar will not work. With the exception of the fluent API (new in SLF4J 2.0.x), from the client's perspective all versions of slf4j-api are compatible. Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M. You only need to ensure that the version of your provider matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used to compile a given dependency in your project. You can always use *any* version of slf4j-api.jar, and as long as the version of slf4j-api.jar and its provider match, you should be fine. Donations and sponsorship You can also support SLF4J/logback/reload4j projects via donations and sponsorship. We thank our current supporters and sponsors for their continued contributions. Sponsorship link: https://github.com/sponsors/qos-ch Announcement mailing list: You can receive SLF4J/logback/reload4j related announcements by subscribing QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki Gülcü

1 0

[JIRA] Updates for SLF4J-554: MessageFormatter refactor (declare field variable, naming, not used variable)
by QOS.CH (JIRA) 15 Aug '22

15 Aug '22

SLF4J / SLF4J-554 [Open] MessageFormatter refactor (declare field variable, naming, not used variable) ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-554 ============================== Issue created ------------------------------ jaehunchoi created this issue on 15/Aug/22 1:32 PM Summary: MessageFormatter refactor (declare field variable, naming, not used variable) Issue Type: Improvement Assignee: SLF4J developers list Created: 15/Aug/22 1:32 PM Priority: Minor Reporter: jaehunchoi Severity: normal Description: I changed three things from MessageFormatter class. First, declare field variables in for-loop. Before I change, field variables named "j", "l" declared out from for-loop. I thought that it was because of the performance. but from performance perspective, It was not faster than declaring in for-loop (rather, the latter was faster). So, I changed these based on a maintenance perspective. "declare where use." Second, There was wrong spelled method in messageFormatter (isEscapedDelimeter -> isEscapedDelimiter). It is only used in same class. So I changed. Last, static char `DELIM_STOP` never used in messageFormatter class. so I deleted. this is my first time to contribute! ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-553: Add GitHub token permissions for GitHub Actions workflow
by QOS.CH (JIRA) 21 Jul '22

21 Jul '22

SLF4J / SLF4J-553 [Resolved] Add GitHub token permissions for GitHub Actions workflow ============================== 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-553 ============================== 1 comment ------------------------------ Varun Sharma on 21/Jul/22 4:10 PM I think it has to do with the order of events. GitHub token permissions were introduced after developers had already started using the token, so having "contents: read" as default later on would have broken some existing workflows that needed higher permissions and had not yet set them explicitly. You can set "contents: read" as default for your repo and org using the UI: https://github.blog/changelog/2021-04-20-github-actions-control-permissions… ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-553: Add GitHub token permissions for GitHub Actions workflow
by QOS.CH (JIRA) 21 Jul '22

21 Jul '22

SLF4J / SLF4J-553 [Resolved] Add GitHub token permissions for GitHub Actions workflow ============================== 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-553 ============================== 2 updates ------------------------------ Changes by Ceki Gülcü on 21/Jul/22 12:48 PM Resolution: Fixed Status: Resolved (was: Open) ============================== 1 comment ------------------------------ Ceki Gülcü on 21/Jul/22 12:50 PM [~varunsh] Thank you for this report. I was wondering why "permissions: contents: read" was not the default. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-553: Add GitHub token permissions for GitHub Actions workflow
by QOS.CH (JIRA) 19 Jul '22

19 Jul '22

SLF4J / SLF4J-553 [Open] Add GitHub token permissions for GitHub Actions workflow ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-553 ============================== Issue created ------------------------------ Varun Sharma created this issue on 19/Jul/22 5:19 PM Summary: Add GitHub token permissions for GitHub Actions workflow Issue Type: Improvement Assignee: SLF4J developers list Created: 19/Jul/22 5:19 PM Environment: GitHub Action workflow at https://github.com/qos-ch/slf4j/blob/master/.github/workflows/main.yml Priority: Major Reporter: Varun Sharma Description: This work has been done as part of PR: [https://github.com/qos-ch/slf4j/pull/293] GitHub recommends defining minimum GITHUB_TOKEN permissions for securing GitHub Actions workflows * [https://github.blog/changelog/2021-04-20-github-actions-control-permissions…] * [https://docs.github.com/en/actions/security-guides/automatic-token-authenti…] * The Open Source Security Foundation (OpenSSF) [Scorecards|https://github.com/ossf/scorecard] treats not setting token permissions as a high-risk issue ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-548: Loading services (plugins) with the caller's ClassLoader
by QOS.CH (JIRA) 06 Jul '22

06 Jul '22

SLF4J / SLF4J-548 [Open] Loading services (plugins) with the caller's ClassLoader ============================== 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-548 ============================== 1 comment ------------------------------ pierre on 06/Jul/22 2:18 PM The fact of having to recompile SLF4J with each update does not really satisfy me. Would it be possible to load the services with the caller's class loader only if it was not found by the thread's class loader? The basic operation remains unchanged, but SLF4J offers the possibility of being embedded in a MANIFEST.MF of a jar archive loader by an URLClassLoader... Thank you. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-552: Disable pattern programatically in current thread.
by QOS.CH (JIRA) 28 Jun '22

28 Jun '22

SLF4J / SLF4J-552 [Closed] Disable pattern programatically in current thread. ============================== 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-552 ============================== 1 comment ------------------------------ Ceki Gülcü on 28/Jun/22 10:31 PM Well done. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0