- slf4j-dev - mailman3.qos.ch

[JIRA] Updates for SLF4J-507: Logger.getLogger (compact initialization)
by QOS.CH (JIRA) 08 Feb '21

08 Feb '21

SLF4J / SLF4J-507 [Open] Logger.getLogger (compact initialization) ============================== 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-507 ============================== Issue created ------------------------------ Sergey Chernov created this issue on 08/Feb/21 8:02 AM Summary: Logger.getLogger (compact initialization) Issue Type: Improvement Affects Versions: 2.0.0-alpha1 Assignee: SLF4J developers list Components: Core API Created: 08/Feb/21 8:02 AM Environment: Manual definition of {{Logger}} field in class. Priority: Minor Reporter: Sergey Chernov Description: Most common use case of logger declaration looks like {code} import org.slf4j.Logger; import org.slf4j.LoggerFactory; ... private static final Logger logger = LoggerFactory.getLogger(CurrentType.class); {code} It's almost fine, but it could be more compact: {code} import org.slf4j.Logger; ... private static final Logger logger = Logger.getLogger(CurrentType.class); {code} Before java 8 it was not possible ({{Logger}} is an interface, not abstract class), now since the minimum required version is 9, the static initialization method can be introduced in the interface. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-497: SLF4JLocationAwareLog avoid building message when logging level is disabled
by QOS.CH (JIRA) 08 Feb '21

08 Feb '21

SLF4J / SLF4J-497 [Open] SLF4JLocationAwareLog avoid building message when logging level is disabled ============================== 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-497 ============================== 1 comment ------------------------------ Ondrej Zizka on 08/Feb/21 2:13 AM Big YES for this feature. JUL has had it that for several years now. And this is the easiest way to avoid string building. E.g. in Kontlin: log.info \{ "Very big entity whose toString() will take a second if called: ${bigEntity}" } ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

JDK 16 is now in the Release Candidate Phase
by Rory O'Donnell 05 Feb '21

05 Feb '21

*Hi Ceki, * *Per the JDK 16 schedule , we are in the Release Candidate Phase**[1] .* *Please advise if you find any issues while testing the latest Early Access builds.* * Schedule for JDK 16 o *2021/02/04 Initial Release Candidate* o 2021/02/18 Final Release Candidate o 2021/03/16 General Availability * Release Notes [2] OpenJDK 16 Early Access build 35**is now available at http://jdk.java.net/16 <http://jdk.java.net/16> * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Features [3] - the overall feature set is frozen. No further JEPs will be targeted to this release. * Changes in recent builds that maybe of interest: o Build 34: + JDK-8259025: Record compact constructor using Objects.requireNonNull # Reported by JUnit5 o Build 32: + JDK-8259014: Incomplete support for Unix domain sockets in Windows 2019 Server * JDK 16 - topics of interest: o Unix domain socket channels (JEP-380) overview: https://inside.java/2021/02/03/jep380-unix-domain-sockets-channels/ <https://inside.java/2021/02/03/jep380-unix-domain-sockets-channels/> o Java Feature Spotlight: Pattern Matching https://inside.java/2021/01/22/feature-spotlight-pattern-matching/ <https://inside.java/2021/01/22/feature-spotlight-pattern-matching/> o Foreign Memory Access - Pulling all the thread https://inside.java/2021/01/25/memory-access-pulling-all-the-threads/ <https://inside.java/2021/01/25/memory-access-pulling-all-the-threads/> * General – topic of interest: o Inside Java Episode 11 “How to contribute to OpenJDK” with Stuart Marks and Jesper Wilhelmsson https://inside.java/2021/01/29/podcast-011/ <https://inside.java/2021/01/29/podcast-011/> Project Lanai EA 9 Build 17-lanai+2-49 (2021/1/20) <http://jdk.java.net/lanai/> is available now * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html> * EA builds are intended for developers looking to test and provide feedback on using Project Lanai. * This is a macOS-specific project which implements a new Java 2D graphics rendering pipeline for macOS. * Project Lanai Wiki: https://wiki.openjdk.java.net/display/lanai/Main <https://wiki.openjdk.java.net/display/lanai/Main> * Please send feedback via e-mail to lanai-dev(a)openjdk.java.net <mailto:lanai-dev@openjdk.java.net>. To send e-mail to this address you must first subscribe to the mailing list <https://mail.openjdk.java.net/mailman/listinfo/lanai-dev>. Project Loom Build 17-loom+2-42 (2021/1/14) <http://jdk.java.net/loom/> based on JDK-17+5 <https://github.com/openjdk/jdk/releases/tag/jdk-17%2B5> is available now * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html> * These builds are intended for developers looking to "kick the tyres" and provide feedback on using the API or by sending bug reports. * API Javadoc : https://download.java.net/java/early_access/loom/docs/api/ <https://download.java.net/java/early_access/loom/docs/api/> * Please send feedback via e-mail to loom-dev(a)openjdk.java.net <mailto:loom-dev@openjdk.java.net>. To send e-mail to this address you must first subscribe to the mailing list <http://mail.openjdk.java.net/mailman/listinfo/loom-dev>. OpenJDK 17 Early Access build 8**is now available at http://jdk.java.net/17 <http://jdk.java.net/17> * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Changes in recent builds that maybe of interest: o Build 8: + JDK-8222850: Misleading cascade compiler error in switch expression with undefined vars # Reported by jOOQ. + JDK-8217633: Configurable extensions with system properties + JDK-8249867: DOM LSSerializer control of newline after XML header + JDK-8256421: Added 2 HARICA Root CA Certificates + JDK-8259801: Enable XML Signature secure validation mode by default o Build 7: + JDK-8165276: Spec states to invoke the premain method in an agent class if it's public but implementation differs + JDK-8256895: Add support for RFC 8954: Online Certificate Status Protocol (OCSP) Nonce Extension o Build 6: + JDK-8259048: (tz) Upgrade time-zone data to tzdata2020f January 2021 Critical Patch Update Released: * As part of the Jan 2021 CPU we released JDK 15.0.2, JDK 11.0.10 LTS, JDK 8u281, and JDK 7u291 as well as OpenJDK 15.0.2 (publicly available). Rgds, Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2021-February/005062.html <https://mail.openjdk.java.net/pipermail/jdk-dev/2021-February/005062.html> [2] https://jdk.java.net/16/release-notes <https://jdk.java.net/16/release-notes> [3] http://openjdk.java.net/projects/jdk/16/ <http://openjdk.java.net/projects/jdk/16/> -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] Updates for SLF4J-506: org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data.
by QOS.CH (JIRA) 02 Feb '21

02 Feb '21

SLF4J / SLF4J-506 [Open] org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data. ============================== 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-506 ============================== Issue created ------------------------------ Simon Mulser created this issue on 02/Feb/21 9:30 AM Summary: org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data. Issue Type: Bug Affects Versions: 1.7.30 Assignee: SLF4J developers list Components: slf4j-ext Created: 02/Feb/21 9:30 AM Environment: https://nvd.nist.gov/vuln/detail/CVE-2018-8088 Priority: Major Reporter: Simon Mulser External issue URL: https://nvd.nist.gov/vuln/detail/CVE-2018-8088 Severity: major ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for SLF4J-505: Ignore Multiple Bindings Warning
by QOS.CH (JIRA) 16 Jan '21

16 Jan '21

SLF4J / SLF4J-505 [Open] Ignore Multiple Bindings Warning ============================== 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-505 ============================== Issue created ------------------------------ DAVID MOLLITOR created this issue on 16/Jan/21 3:27 PM Summary: Ignore Multiple Bindings Warning Issue Type: Improvement Assignee: SLF4J developers list Created: 16/Jan/21 3:27 PM Priority: Major Reporter: DAVID MOLLITOR Description: {quote}SLF4J API is designed to bind with one and only one underlying logging framework at a time. If more than one binding is present on the class path, SLF4J will emit a warning, listing the location of those bindings. The warning emitted by SLF4J is just that, a warning. {quote} Please add a command-line option {{-D}} to silence this particular warning in regards to _multiple bindings were found on the class path_. I have a command-line tool that loads JAR files (including uber JARs) at runtime and sometimes the JAR files contains an SLF4J logger implementation. It is annoying and scary for users to see this warning when they run this command line tool. I understand that these are just warnings, and that it does not affect the operation of the tool, but I would like a way to "acknowledge" these warnings so that they are not printed at all. Since these JARs are loaded at run-time, it is not possible to change the POM/Graddle files to exclude them. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

JDK 16 is now in Rampdown Phase Two
by Rory O'Donnell 15 Jan '21

15 Jan '21

Hi Ceki, *Per the JDK 16 schedule , we are in Rampdown Phase Two* *[1] . * *Please advise if you find any issues while testing the latest Early Access builds.* * Schedule for JDK 16 o *2021/01/14 Rampdown Phase Two* o 2021/02/04 Initial Release Candidate o 2021/02/18 Final Release Candidate o 2021/03/16 General Availability * Release Notes [2] OpenJDK 16 Early Access build 32**is now available at http://jdk.java.net/16 * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Features [3] - the overall feature set is frozen. No further JEPs will be targeted to this release. * Changes in recent builds that maybe of interest: o Build 32: + JDK-8259028 - ClassCastException when using custom filesystem with wrapper FileChannel impl # Apache Lucene found. + JDK-8253996 - Javac error on jdk16 build 18: invalid flag: -Xdoclint:-missing # Apache Zookeeper found. o Build 31: + JDK-8259027: NullPointerException in makeMappedSegment due to NULL Unmapper when length of segment is 0 # Reported by Apache Lucene o Build 30: + JDK-8254023: A module declaration is not allowed to be a target of an annotation that lacks an @Target meta-annotation # Reported by JUnit5 + JDK-8256693: getAnnotatedReceiverType parameterizes types too eagerly * JDK 16 - topics of interest o Investigating MD5 overheads: https://cl4es.github.io/2021/01/04/Investigating-MD5-Overheads.html o Towards OpenJDK 17 - a quick update on startup performance https://cl4es.github.io/2020/12/06/Towards-OpenJDK-17.html o Migrating OpenJDK to Git & GitHub - GitHub Universe 2020 session replay https://inside.java/2020/12/11/skara-github-universe/ Project Panama/foreign EA Build 16-panama+3-385 (2020/12/10) <https://jdk.java.net/panama/> is available now [4] * What's new o jextract is now fully compatible with Java 16 o New architecture based on Foreign-Memory Access API (JEP 370 <https://openjdk.java.net/jeps/370>, JEP 383 <https://openjdk.java.net/jeps/383>, JEP 393 <https://openjdk.java.net/jeps/393>) and Foreign Linker API (JEP 389 <https://openjdk.java.net/jeps/389>) * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html> * EA builds are produced for the purpose of gathering feedback. Use for any other purpose is at your own risk. * Please send feedback via e-mail to panama-dev(a)openjdk.java.net <panama-dev(a)openjdk.java.net>. To send e-mail to this address you must first subscribe to the mailing list <https://mail.openjdk.java.net/mailman/listinfo/panama-dev>. * Project Panama - topics of interest o “The Vector API” with John Rose and Paul Sandoz https://inside.java/2020/11/17/podcast-007/ o “The Foreign Memory Access API” with Maurizio Cimadamore and Jorn Vernee https://inside.java/2020/12/11/podcast-009/ o “The Foreign Linker API” with Maurizio Cimadamore and Jorn Vernee https://inside.java/2020/12/21/podcast-010/ OpenJDK 17 Early Access build 5**is now available at http://jdk.java.net/17 * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Changes in recent builds that maybe of interest: o Build 4: + JDK-8258800: Deprecate -XX:+AlwaysLockClassLoader o Build 3: + JDK-8246005: KeyStoreSpi::engineStore(LoadStoreParameter) spec mismatch to its behavior + JDK-8258765: getAnnotatedReceiverType parameterizes types too eagerly * JDK 17 - topic of interest o Towards OpenJDK 17 - a quick update on startup performance: + https://cl4es.github.io/2020/12/06/Towards-OpenJDK-17.html Java Cryptographic Roadmap [5] has been updated * Removing root certificates with 1024-bit keys in July 2021 CPU. * Disabling of SHA-1 JARS signed after 2019-01-01 has been postponed to July 2021 CPU. Rgds, Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2021-January/005001.html [2] https://jdk.java.net/16/release-notes [3] http://openjdk.java.net/projects/jdk/16/ <http://openjdk.java.net/projects/jdk/16/> [4] https://mail.openjdk.java.net/pipermail/panama-dev/2020-December/011605.html <https://mail.openjdk.java.net/pipermail/panama-dev/2020-December/011605.html> [5] https://java.com/en/jre-jdk-cryptoroadmap.html <https://java.com/en/jre-jdk-cryptoroadmap.html>

1 0

JDK 16 is in Rampdown Phase One
by Rory O'Donnell 13 Dec '20

13 Dec '20

Hi Ceki, *Per the JDK 16 schedule , we are in Rampdown Phase One* *[1] . * *Please advise if you find any issues while testing the latest Early Access builds.* * Schedule for JDK 16 o *2020/12/10 Rampdown Phase One* o 2021/01/14 Rampdown Phase Two o 2021/02/04 Initial Release Candidate o 2021/02/18 Final Release Candidate o 2021/03/16 General Availability * Release Notes [2] OpenJDK 16 Early Access build 28**is now available at http://jdk.java.net/16 * Features - the overall feature set is frozen. No further JEPs will be targeted to this release. * Significant Integrations in b28: o *Integrated JEP 396: **Strongly Encapsulate JDK Internals by Default <https://openjdk.java.net/jeps/396>** * + Strongly encapsulate all internal elements of the JDK by default, except for critical internal APIs <https://openjdk.java.net/jeps/260#Description> such as |sun.misc.Unsafe|. + Allow end users to choose the relaxed strong encapsulation that has been the default since JDK 9. o Integrated JEP 397: Sealed Classes (Second Preview) <https://openjdk.java.net/jeps/397> with this release. + Enhance the Java programming language with sealed classes and interfaces <https://cr.openjdk.java.net/~briangoetz/amber/datum.html>. + Refines JEP 360 <https://openjdk.java.net/jeps/360> which was delivered in JDK 15 as a preview feature. * These early-access , open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Changes in recent builds that maybe of interest: o Build 28 + JDK-8256299: JEP 396: Strongly Encapsulate JDK Internals by Default + JDK-8166596: TLS support for the EdDSA signature algorithm + JDK-8256718: Old tracing flags are now obsolete and must be replaced with unified logging o Build 27 + JDK-8159746: (proxy) Support for default methods + JDK-8254631: Better support ALPN byte wire values in SunJSSE Project Loom Early-Access: *Build 16-loom+9-316 <http://jdk.java.net/loom/>* (2020/11/30) - based on JDK-16+25 <https://github.com/openjdk/jdk/releases/tag/jdk-16%2B25> * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html> * These builds are intended for developers looking to "kick the tyres" and provide feedback on using the API or by sending bug reports. * Please send feedback via e-mail to loom-dev(a)openjdk.java.net <mailto:loom-dev@openjdk.java.net>. To send e-mail to this address you must first subscribe to the mailing list <http://mail.openjdk.java.net/mailman/listinfo/loom-dev>. Rgds, Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2020-December/004991.html [2] https://jdk.java.net/16/release-notes

1 0

[JIRA] Updates for SLF4J-493: Lambda expression call with log4j logs the wrong line number
by QOS.CH (JIRA) 11 Dec '20

11 Dec '20

SLF4J / SLF4J-493 [Open] Lambda expression call with log4j logs the wrong line number ============================== 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-493 ============================== 1 comment ------------------------------ Daniel Gray on 11/Dec/20 3:36 PM I've looked more into this and it seems to be a bug in the log4j2 SLF4J bridge. I'll open a bug report there. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] SLF4J-504: New methods for Kotlin (scala?) developers.
by Aleksey Tomin 03 Dec '20

03 Dec '20

Hi for all What do you think about new methods in Logger interface for kotlin/scala developers? We want to use logger.trace { "Message with $parameter" } instead of logger.trace("Message with {}", parameter) It will be allowed when methods like default void trace(Supplier<String> msgSupplier) { if (isTraceEnabled()) { trace(msgSupplier.get()); } } will be added info org.slf4j.Logger interface. I've done the first part of this in https://github.com/qos-ch/slf4j/pull/253 and I will to done all of this if someone want to review.

1 0

[JIRA] Updates for SLF4J-504: Add methods with Supplier into Logger methods
by QOS.CH (JIRA) 03 Dec '20

03 Dec '20

SLF4J / SLF4J-504 [Open] Add methods with Supplier into Logger methods ============================== 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-504 ============================== Issue created ------------------------------ Aleksey Tomin created this issue on 03/Dec/20 9:30 AM Summary: Add methods with Supplier into Logger methods Issue Type: Improvement Assignee: SLF4J developers list Created: 03/Dec/20 9:30 AM Labels: logging Priority: Major Reporter: Aleksey Tomin Description: In kotlin we want to use {{}} {code:java} logger.trace { "Message with $parameter" }{code} {{}}instead of {{}} {code:java} logger.trace("Message with {}", parameter){code} {{}} I suggest adding default method *Logger.trace* (debug, etc) with trivial implementations like https://github.com/qos-ch/slf4j/pull/253 ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0