August 2018 - slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-442) Integrate with java.lang.System.Logger/LoggerFinder (JEP 264)
by QOS.CH (JIRA) 29 Aug '18

29 Aug '18

Nicolai Parlog created SLF4J-442: ------------------------------------ Summary: Integrate with java.lang.System.Logger/LoggerFinder (JEP 264) Key: SLF4J-442 URL: https://jira.qos.ch/browse/SLF4J-442 Project: SLF4J Issue Type: New Feature Environment: Java 9+ Reporter: Nicolai Parlog Assignee: SLF4J developers list [JEP 264: Platform Logging API and Service|http://openjdk.java.net/jeps/264] introduced a mechanism to Java 9 that allows third-party logging frameworks to handle JDK log messages (like those Swing produces; _not_ JVM messages). SLF4J should integrate with it. There is already [a proof of concept|https://github.com/nicolaiparlog/slf4j/commit/e0c7780bdae254535a6e9…] -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Integrate with platform logging (JEP 264)
by Nicolai Parlog 28 Aug '18

28 Aug '18

Hi! JEP 264[1] allows logging frameworks to handle JDK log messages like those from Swing. Integrating SLF4J with it is fairly straightforward[2] and I'm happy to update my code and create a PR if there's any interest. so long ... Nicolai [1] http://openjdk.java.net/jeps/264 [2] https://github.com/nicolaiparlog/slf4j/commit/e0c7780bdae254535a6e9c053b2af… -- PGP Key: http://keys.gnupg.net/pks/lookup?op=vindex&search=0xCA3BAD2E9CCCD509 Web: http://blog.codefx.org a blog about software development https://courses.codefx.org high-quality Java courses Social: https://twitter.com/nipafx http://youtube.com/c/codefx

2 1

JDK 11: First Release Candidate available
by Rory O'Donnell 24 Aug '18

24 Aug '18

Hi Ceki, *JDK 11 build 28 is our first JDK 11 Release Candidate [1] * * JDK 11 Early Access build 28 is available at : - jdk.java.net/11/ *FOSS fixes in recent builds.* * Eclipse Jetty - JDK-8207177 <https://bugs.openjdk.java.net/browse/JDK-8207177> (b27) * Apache Tomcat -JDK-8208642 <https://bugs.openjdk.java.net/browse/JDK-8208642>(b27) * Netty - JDK-8207029 <https://bugs.openjdk.java.net/browse/JDK-8207029> (b23), JDK-8208166 <https://bugs.openjdk.java.net/browse/JDK-8208166> (b25) *JDK 12 Early Access build 8 is available at : - jdk.java.net/12/* * Release Notes for JDK 12 [2] * Changes in this build include o JDK-8208350 <https://bugs.openjdk.java.net/browse/JDK-8208350> - Disable all DES TLS cipher suites *OpenJFX Early-Access Build 24 is available at :-* *http://jdk.java.net/openjfx/* * This library is delivered as a set of modules, along with the native code needed to run JavaFX, that can be run using a JDK 10 <http://jdk.java.net/10/> build or a JDK 11 EA <http://jdk.java.net/11/> build. * This build is intended to allow application developers and OpenJFX contributors to test their applications with an unbundled, standalone JavaFX library. Regards, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-August/001844.html <http://openjdk.java.net/projects/jdk/11/#Schedule> [2] http://jdk.java.net/12/release-notes -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (SLF4J-441) XLogger exit() method is not backward compatible after we update SLF4J API to 1.7.25
by QOS.CH (JIRA) 14 Aug '18

14 Aug '18

Ramesh created SLF4J-441: ---------------------------- Summary: XLogger exit() method is not backward compatible after we update SLF4J API to 1.7.25 Key: SLF4J-441 URL: https://jira.qos.ch/browse/SLF4J-441 Project: SLF4J Issue Type: Bug Components: Core API Affects Versions: 1.7.25 Environment: JDK 1.8 Maven Eclipse Jetty plugin 9.4.8.v20180619 SLF4J API - 1.7.25 SLF4J EXT - 1.7.25 Reporter: Ramesh Assignee: SLF4J developers list Our code has the below code in different places with different version of exit() method. LOGGER.exit() LOGGER.exit(Object) LOGGER.exit(booleanValue) We are currently using SLF4J API 1.7.2 and now we are trying to update to SLF4J 1.7.25 to address one security vulnerability issue. During update, we are seeing this exception {color:#ff0000}Caused by: java.lang.NoSuchMethodError: org.slf4j.ext.XLogger.exit(Ljava/lang/Object;)V{color} {color:#ff0000}{color:#333333}Seems XLogger exit() method is enhanced in 1.7.6 and see the method signature is changed from{color} public void exit(Object result) \{{color} {color:#ff0000}}{color} {color:#ff0000}{color:#333333}to{color} {color} {color:#ff0000}public <T> T exit(T result) \{{color} {color:#ff0000}}{color} {color:#333333}I think this change is not backward compatible and we could not able to update the SLF4J version.{color} {color:#333333}Is it possible to make the change backward compatible? Or Please suggest how we can overcome the exception during update?{color} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 11 , JDK 12 and JDK 8u192 Early Access builds are available on jdk.java.net
by Rory O'Donnell 07 Aug '18

07 Aug '18

Hi Ceki, *JDK 11 Early Access build 25 is available at : - **jdk.java.net/11/* * *JDK 11 entered Rampdown Phase 2 on 26-July [1]* o The overall feature set is frozen. No further JEPs will be targeted to this release. o We now turn our focus to P1 and P2 bugs. * Release notes are available here [2] *JDK 12 Early Access build 05 is available at : - **jdk.java.net/12/* * Changes in this build here <http://hg.openjdk.java.net/jdk/jdk/log?revcount=10000&rev=reverse%28%22jdk-…>. *JDK 8u192 Early Access build 04 is available at : - http://jdk.java.net/8/* * JDK 8u192 timeline is available [3] o GA is scheduled for October 2018 **Conference videos online* * * *OpenJDK Committers’ Workshop [4]* * JVM Language Summit 2018 [5]: Regards, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-July/001669.html [2] http://jdk.java.net/11/release-notes [3] http://openjdk.java.net/projects/jdk8u/releases/8u192.html [4] https://www.youtube.com/playlist?list=PLX8CzqL3ArzXY_9Ornabhxs-j2h4hnvJ3 [5] https://www.youtube.com/playlist?list=PLX8CzqL3ArzVnxC6PYxMlngEMv3W1pIkn -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (SLF4J-371) Support the lambda expression in the Logger
by QOS.CH (JIRA) 03 Aug '18

03 Aug '18

[ https://jira.qos.ch/browse/SLF4J-371?page=com.atlassian.jira.plugin.system.… ] Gleb Beliaev commented on SLF4J-371: ------------------------------------ +1 its cool for Java 8. > Support the lambda expression in the Logger > ------------------------------------------- > > Key: SLF4J-371 > URL: https://jira.qos.ch/browse/SLF4J-371 > Project: SLF4J > Issue Type: Improvement > Components: Core API > Affects Versions: 1.7.22 > Reporter: MiNG > Assignee: SLF4J developers list > > In some cases, we don't want to calculate the expression for logging eagerly cause the performance reason. Then, we would write the code like the following: > {code:java} > if (LOGGER.isWarnEnabled()) > { > LOGGER.warn("some message: {}", Json.serialize(obj)); > }{code} > Before JDK8, there is no way to encapsulate the above code, because the expression is always calculated before passed as an argument. So, many "if"s appear in the code and smell badly. > Now, the lambda expression is supported by JDK8, the above could be simplified like following: > {code:java} > LOGGER.warn(formatter -> formatter.format("some message: {}", Json.serialize(obj)));{code} > With the default method definition in the org.slf4j.Logger: > {code:java} > public interface Logger > { > default void warn(Function<MessageFormatter, String> messageSupplier) > { > if (this.isWarnEnabled()) > { > /* Calculate the expression only if the WARN level logging is enabled. */ > this.warn(messageSupplier.apply(this.getFormatter())); > } > } > }{code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0