November 2019 - slf4j-dev - mailman3.qos.ch

JDK 14 - Early Access build 25 is available
by Rory O'Donnell 29 Nov '19

29 Nov '19

Hi Ceki, *OpenJDK builds - JDK 14 *- Early Access build 25 is available at http://jdk.java.net/14/ 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>. * *Next Milestone* ** o ** *12-Dec-2019 Rampdown Phase One.* * Release notes o https://jdk.java.net/14/release-notes * JEP proposed to target JDK 14 o JEP 365 ZGC on Windows <https://openjdk.java.net/jeps/365> * JEPs targeted to JDK 14, so far: o JEP 305: Pattern Matching for instanceof (Preview) <http://openjdk.java.net/jeps/305> was proposed to target. o JEP 343: Packaging Tool (Incubator) <http://openjdk.java.net/jeps/343> was proposed to target. o JEP 345: NUMA-Aware Memory Allocation for G1 <http://openjdk.java.net/jeps/345> was integrated. o JEP 349: JFR Event Streaming <http://openjdk.java.net/jeps/349> was integrated. o JEP 352: Non-Volatile Mapped Byte Buffers <http://openjdk.java.net/jeps/352> was targeted. o JEP 358: Helpful NullPointerExceptions <https://openjdk.java.net/jeps/358> was integrated. o JEP 359: Records (Preview) <http://openjdk.java.net/jeps/359> JEP 359: Records (Preview) <http://openjdk.java.net/jeps/359> was proposed to target. o JEP 361: Switch Expressions (Standard) <http://openjdk.java.net/jeps/361> was intergrated. o JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector <http://openjdk.java.net/jeps/363> was targeted. o JEP 364: ZGC on macOS <http://openjdk.java.net/jeps/364> was targeted. o JEP 366: Deprecate the ParallelScavenge + SerialOld GC Combination <http://openjdk.java.net/jeps/366> was proposed to target. o JEP 367: Remove the Pack200 Tools and API <http://openjdk.java.net/jeps/367> was targeted to JDK 14. o JEP 368: Text Blocks (Second Preview) <http://openjdk.java.net/jeps/368> was proposed to target. * Recent Bug fixes of Interest * Build 25: o JDK-8233301: Implementation of JEP 366: Deprecate the ParallelScavenge + SerialOld GC Combination o JDK-8233296: The behavior of MulticastSocket getOption/setOption for IP_MULTICAST_LOOP is changed to conform the specification of StandardSocketOptions.IP_MULTICAST_LOOP * Build 24: o JDK-8233141 :DatagramSocket.send and MulticastSocket.send throw IllegalArgumentException when the socket is not connected and the packet doesn't contain any address ) o JDK-8214024: Remove the default keytool -keyalg value o JDK-8232019: Add LuxTrust certificate updates to the existing root program * Build 23 o JDK 8232365: Implementation for JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector o JDK 8224817: Implementation of JEP 364: ZGC on macOS * Changes in this build <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B24%22%3A%3…> *jpackage EA -* Build 14-jpackage+1-70 (2019/11/12) * This is an early access build of JEP 343: Packaging Tool <https://openjdk.java.net/jeps/343>, aimed at testing a prototype implementation of jpackage, which is a new tool for packaging self-contained Java applications along with a Java Runtime Environment. * 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> * Build is now available http://jdk.java.net/jpackage/ * Please send feedback via e-mail to core-libs-dev(a)openjdk.java.net <mailto:core-libs-dev@openjdk.java.net> Rgds,Rory** ** -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] (SLF4J-477) Add New Exception for Stack Trace Dumps
by QOS.CH (JIRA) 22 Nov '19

22 Nov '19

[ https://jira.qos.ch/browse/SLF4J-477?page=com.atlassian.jira.plugin.system.… ] DAVID MOLLITOR commented on SLF4J-477: -------------------------------------- Alternatively, provide some sort of static token or marker that produces a stack trace so that the stack trace is only collected if the logging level is enabled. > Add New Exception for Stack Trace Dumps > --------------------------------------- > > Key: SLF4J-477 > URL: https://jira.qos.ch/browse/SLF4J-477 > Project: SLF4J > Issue Type: New Feature > Reporter: DAVID MOLLITOR > Assignee: SLF4J developers list > > I have seen many examples where developers want to dump a stack trace to the log system simply to track the execution path of the Thread and not associated with any real issue. > {code:java} > LOG.trace("Stack Trace Dump", new Exception()); > {code} > The output is something like: > {code:none} > 2019-11-19T08:13:31,392 TRACE [Logger] Class: Stack Trace Dump > java.lang.Exception: null > at > ... > {code} > > I would like to propose that SLF4J ships with an {{Exception}} class specific to this scenario. A user could easily mistake this as logging as being related to a real error condition instead of its intended informational purpose because it has the word 'Exception' in it and may be interpreted as being related to an erroneous 'null' value. > > {code:java} > LOG.trace("Stack Trace Dump", new StackTraceDump()); > 2019-11-19T08:13:31,392 TRACE [Logger] Class: Stack Trace Dump > ch.qos.slf4f.StackTraceDump: Dumping stack trace > at > ... > {code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-477) Add New Exception for Stack Trace Dumps
by QOS.CH (JIRA) 20 Nov '19

20 Nov '19

DAVID MOLLITOR created SLF4J-477: ------------------------------------ Summary: Add New Exception for Stack Trace Dumps Key: SLF4J-477 URL: https://jira.qos.ch/browse/SLF4J-477 Project: SLF4J Issue Type: New Feature Environment: I have seen many examples where developers want to dump a stack trace to the log system simply to track the execution path of the Thread and not associated with any real issue. {code:java} LOG.trace("Stack Trace Dump", new Exception()); {code} The output is something like: {code:none} 2019-11-19T08:13:31,392 TRACE [Logger] Class: Stack Trace Dump java.lang.Exception: null at ... {code} I would like to propose that SLF4J ships with an {{Exception}} class specific to this scenario. A user could easily mistake this as logging as being related to a real error condition instead of its intended informational purpose because it has the word 'Exception' in it and may be interpreted as being related to an erroneous 'null' value. {code:java} LOG.trace("Stack Trace Dump", new StackTraceDump()); 2019-11-19T08:13:31,392 TRACE [Logger] Class: Stack Trace Dump ch.qos.slf4f.StackTraceDump: Dumping stack trace at ... {code} Reporter: DAVID MOLLITOR Assignee: SLF4J developers list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-476) slf4j-log4j12 Add isLog4JLogger Utility
by QOS.CH (JIRA) 16 Nov '19

16 Nov '19

DAVID MOLLITOR created SLF4J-476: ------------------------------------ Summary: slf4j-log4j12 Add isLog4JLogger Utility Key: SLF4J-476 URL: https://jira.qos.ch/browse/SLF4J-476 Project: SLF4J Issue Type: Improvement Environment: https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-co… Reporter: DAVID MOLLITOR Assignee: SLF4J developers list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 14 - Early Access build 22 is available
by Rory O'Donnell 12 Nov '19

12 Nov '19

Hi Ceki, *OpenJDK builds - JDK 14 *- Early Access build 22 is available at http://jdk.java.net/14/ 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>. * Release notes o https://jdk.java.net/14/release-notes * JEPs targeted to JDK 14, so far: * JEP 345: NUMA-Aware Memory Allocation for G1 <http://openjdk.java.net/jeps/345> was Targeted to JDK 14. * JEP 349: JFR Event Streaming <http://openjdk.java.net/jeps/349> was Integrated. * JEP 361: Switch Expressions (Standard) <http://openjdk.java.net/jeps/361> was Targeted to JDK 14. * JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector <http://openjdk.java.net/jeps/363> was Targeted to JDK 14. * JEP 364: ZGC on macOS <http://openjdk.java.net/jeps/364> was Targeted to JDK 14. * JEP 365: ZGC on Windows <http://openjdk.java.net/jeps/365> moved to Candidate. * JEP 366: Deprecate the ParallelScavenge + SerialOld GC Combination <http://openjdk.java.net/jeps/366> was Proposed to target JDK 14. * JEP 367: Remove the Pack200 Tools and API <http://openjdk.java.net/jeps/367> was Targeted to JDK 14. * JEP 368: Text Blocks (Second Preview) <http://openjdk.java.net/jeps/368> moved to Candidate. * Changes in this build <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B21%22%3A%3…> *jpackage EA -* Build 14-jpackage+1-67 (2019/11/4) * This is an early access build of JEP 343: Packaging Tool <https://openjdk.java.net/jeps/343>, aimed at testing a prototype implementation of jpackage, which is a new tool for packaging self-contained Java applications along with a Java Runtime Environment. * 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> * Build 14 is now available http://jdk.java.net/jpackage/ * Please send feedback via e-mail to core-libs-dev(a)openjdk.java.net <mailto:core-libs-dev@openjdk.java.net> -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[qos-ch/slf4j] 9a3f1f: latest stable is 1.7.29
by Ceki Gulcu 04 Nov '19

04 Nov '19

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 9a3f1f4928ab9d0e0f423e377bec9754507d9e8e https://github.com/qos-ch/slf4j/commit/9a3f1f4928ab9d0e0f423e377bec9754507d… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2019-11-04 (Mon, 04 Nov 2019) Changed paths: M pom.xml M slf4j-site/src/site/pages/download.html M slf4j-site/src/site/pages/news.html Log Message: ----------- latest stable is 1.7.29

1 0

[qos-ch/slf4j]
by Ceki Gulcu 04 Nov '19

04 Nov '19

Branch: refs/tags/v_1.7.29 Home: https://github.com/qos-ch/slf4j

1 0

[JIRA] (SLF4J-442) Integrate with java.lang.System.Logger/LoggerFinder (JEP 264)
by QOS.CH (JIRA) 02 Nov '19

02 Nov '19

[ https://jira.qos.ch/browse/SLF4J-442?page=com.atlassian.jira.plugin.system.… ] Nicolai Parlog commented on SLF4J-442: -------------------------------------- Hey Rüdiger, fancy meeting you here. :) In case you missed it: [this|https://github.com/nicolaiparlog/slf4j/commit/e0c7780bdae254535a6e9c05…] should be a good starting point for a PR. > 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: Ceki Gülcü > Fix For: 2.0.0-alpha2 > > > [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

[JIRA] (SLF4J-442) Integrate with java.lang.System.Logger/LoggerFinder (JEP 264)
by QOS.CH (JIRA) 02 Nov '19

02 Nov '19

[ https://jira.qos.ch/browse/SLF4J-442?page=com.atlassian.jira.plugin.system.… ] Rüdiger zu Dohna commented on SLF4J-442: ---------------------------------------- Hi Ceki. A pull request wouldn't be too much work, but I'd like to hear your opinion on the topic first. > 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: Ceki Gülcü > Fix For: 2.0.0-alpha2 > > > [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