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

Release Announcement: General Availability of JDK 10
by Rory O'Donnell 21 Mar '18

21 Mar '18

Hi Ceki, A number of items to share with you today : *1) JDK 10 General Availability * JDK 10, the first release produced under the six-month rapid-cadence release model [1][2], is now Generally Available. We've identified no P1 bugs since we promoted build 46 almost two weeks ago, so that is the official GA release, ready for production use. GPL'd binaries from Oracle are available here: http://jdk.java.net/10 This release includes twelve features: * 286: Local-Variable Type Inference <http://openjdk.java.net/jeps/286> * 296: Consolidate the JDK Forest into a Single Repository <http://openjdk.java.net/jeps/296> * 304: Garbage-Collector Interface <http://openjdk.java.net/jeps/304> * 307: Parallel Full GC for G1 <http://openjdk.java.net/jeps/307> * 310: Application Class-Data Sharing <http://openjdk.java.net/jeps/310> * 312: Thread-Local Handshakes <http://openjdk.java.net/jeps/312> * 313: Remove the Native-Header Generation Tool (javah) <http://openjdk.java.net/jeps/313> * 314: Additional Unicode Language-Tag Extensions <http://openjdk.java.net/jeps/314> * 316: Heap Allocation on Alternative Memory Devices <http://openjdk.java.net/jeps/316> * 317: Experimental Java-Based JIT Compiler <http://openjdk.java.net/jeps/317> * 319: Root Certificates <http://openjdk.java.net/jeps/319> * 322: Time-Based Release Versioning <http://openjdk.java.net/jeps/322> *2) JDK 11 EA build 5, under both the GPL and Oracle EA licenses, are now available at **http://jdk.java.net/11**.* * Schedule, status & features o http://openjdk.java.net/projects/jdk/11/ * Release Notes: o http://jdk.java.net/11/release-notes * Summary of changes o https://download.java.net/java/early_access/jdk11/5/jdk-11+5.html *3) The Z Garbage Collector Project, early access builds available : * The first EA binary from from The Z Garbage Collector Project, also known as ZGC, is now available. ZGC is a scalable low latency garbage collector. For information on how to enable and use ZGC, please see the project wiki. * Project page: http://openjdk.java.net/projects/zgc/ * Wiki: https://wiki.openjdk.java.net/display/zgc/Main *4) Quality Outreach Report for **March 2018 **is available * * https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+March… *5) **Java Client Roadmap Update * * We posted a blog [3] and related white paper [4] detailing our plans for the Java Client. Rgds,Rory [1] https://mreinhold.org/blog/forward-faster [2] http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html [3] Blog: https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other… [4] Whitepaper: http://www.oracle.com/technetwork/java/javase/javaclientroadmapupdate2018ma… -- 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) 20 Mar '18

20 Mar '18

[ https://jira.qos.ch/browse/SLF4J-371?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-371: ---------------------------------- Planned for the end of 2018. > 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

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

20 Mar '18

[ https://jira.qos.ch/browse/SLF4J-371?page=com.atlassian.jira.plugin.system.… ] Thalys de Aguiar Gomes commented on SLF4J-371: ---------------------------------------------- Hi Guys, Please, any final decision? Do you will or not add the lambda for lazy support? I'm looking forward to removing that if (isXXXenabled) all over the projects > 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

[qos-ch/slf4j] 34486e: SLF4J-431
by Ceki Gulcu 20 Mar '18

20 Mar '18

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 34486e4ea5ec6a4960930a239e80f868f1bf66e3 https://github.com/qos-ch/slf4j/commit/34486e4ea5ec6a4960930a239e80f868f1bf… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-03-20 (Tue, 20 Mar 2018) Changed paths: M slf4j-ext/src/main/java/org/slf4j/ext/EventException.java M slf4j-site/src/site/pages/news.html Log Message: ----------- SLF4J-431

1 0

[JIRA] (SLF4J-428) automatic module name for jul-to-slf4j contains illegal token
by QOS.CH (JIRA) 16 Mar '18

16 Mar '18

[ https://jira.qos.ch/browse/SLF4J-428?page=com.atlassian.jira.plugin.system.… ] Rob Platt commented on SLF4J-428: --------------------------------- Hi Ceki. Would it be possible to get out 1.8.0-beta2 with the already fixed issues in it, and move the open issues to a beta3? Seems like there is quite some work remaining in the release, but this particular fix makes a really big difference when modularizing a project. We could create our own internal package, and will if it comes to it, but I thought there was no harm in asking in case others in the community are looking forward to this fix too :) > automatic module name for jul-to-slf4j contains illegal token > ------------------------------------------------------------- > > Key: SLF4J-428 > URL: https://jira.qos.ch/browse/SLF4J-428 > Project: SLF4J > Issue Type: Bug > Components: jul-to-slf4j > Affects Versions: 1.8.0-beta1 > Reporter: Peter-Josef Meisch > Assignee: Ceki Gülcü > Fix For: 1.8.0-beta2 > > > the automatic module name that is created in Java 9 for the jul-to-slf4 jar is _jul.to.slf4j(a)1.8.0-beta1_. This contains the token *to* which is a reserved word in Java 9 so the generated name cannot be used in requires statements in modul-info.java files of projects using jul-to-slf4j and inhibits migration of projects to Java 9. > This should be modified by adding > {{Automatic-Module-Name: jul_to_slf4j}} > to the manifest for the archive. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-431) Mark EventData as deprecated in preparation for its removal
by QOS.CH (JIRA) 14 Mar '18

14 Mar '18

[ https://jira.qos.ch/browse/SLF4J-431?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-431. ------------------------------ Resolution: Fixed Fixed in [commit d2b27|https://github.com/qos-ch/slf4j/commit/d2b27fba88e983] > Mark EventData as deprecated in preparation for its removal > ----------------------------------------------------------- > > Key: SLF4J-431 > URL: https://jira.qos.ch/browse/SLF4J-431 > Project: SLF4J > Issue Type: Sub-task > Reporter: Ceki Gülcü > Assignee: SLF4J developers list > Fix For: 1.8.0-beta2 > > -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 9b536f: news on SLF4J-431
by Ceki Gulcu 14 Mar '18

14 Mar '18

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 9b536f4259adf2f01852e86306a3a2d7e4a238c0 https://github.com/qos-ch/slf4j/commit/9b536f4259adf2f01852e86306a3a2d7e4a2… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-03-14 (Wed, 14 Mar 2018) Changed paths: M slf4j-site/src/site/pages/news.html Log Message: ----------- news on SLF4J-431

1 0

[qos-ch/slf4j] d2b27f: fix SLF4J-431
by Ceki Gulcu 14 Mar '18

14 Mar '18

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: d2b27fba88e983f921558da27fc29b5f5d269405 https://github.com/qos-ch/slf4j/commit/d2b27fba88e983f921558da27fc29b5f5d26… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-03-14 (Wed, 14 Mar 2018) Changed paths: M slf4j-ext/src/main/java/org/slf4j/ext/EventData.java Log Message: ----------- fix SLF4J-431

1 0

[JIRA] (SLF4J-431) Mark EventData as deprecated
by QOS.CH (JIRA) 13 Mar '18

13 Mar '18

Ceki Gülcü created SLF4J-431: -------------------------------- Summary: Mark EventData as deprecated Key: SLF4J-431 URL: https://jira.qos.ch/browse/SLF4J-431 Project: SLF4J Issue Type: Sub-task Reporter: Ceki Gülcü Assignee: SLF4J developers list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 0ec1f6: remove autoads.js
by Ceki Gulcu 13 Mar '18

13 Mar '18

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 0ec1f6aac8648e87a7dda2f5730fef6db3b4fa33 https://github.com/qos-ch/slf4j/commit/0ec1f6aac8648e87a7dda2f5730fef6db3b4… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2018-03-13 (Tue, 13 Mar 2018) Changed paths: M slf4j-site/src/site/pages/bug-reporting.html M slf4j-site/src/site/pages/codes.html M slf4j-site/src/site/pages/docs.html M slf4j-site/src/site/pages/download.html M slf4j-site/src/site/pages/faq.html M slf4j-site/src/site/pages/index.html M slf4j-site/src/site/pages/legacy.html M slf4j-site/src/site/pages/manual.html M slf4j-site/src/site/pages/migrator.html M slf4j-site/src/site/pages/news.html R slf4j-site/src/site/pages/templates/autoads.js Log Message: ----------- remove autoads.js

1 0