April 2017 - slf4j-dev - mailman3.qos.ch

[JIRA] (SLF4J-371) Support the lambda expression in the Logger
by QOS.CH (JIRA) 28 Apr '17

28 Apr '17

[ https://jira.qos.ch/browse/SLF4J-371?page=com.atlassian.jira.plugin.system.… ] Mariano Ruiz commented on SLF4J-371: ------------------------------------ I agree with @HermanBovens that would be better support the same API than _Log4j2_. > 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: > ``` > if (LOGGER.isWarnEnabled()) > { > LOGGER.warn("some message: {}", Json.serialize(obj)); > } > ``` > 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: > ``` > LOGGER.warn(formatter -> formatter.format("some message: {}", Json.serialize(obj))); > ``` > With the default method definition in the org.slf4j.Logger: > ``` > 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())); > } > } > } > ``` -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 9 EA Build 167 and JDK 8u152 build 03 are available on jdk.java.net
by Rory O'Donnell 28 Apr '17

28 Apr '17

Hi Ceki, *JDK 9 Early Access* build 167 is available at the new location : - jdk.java.net/9/ A summary of all the changes in this build are listed here <http://download.java.net/java/jdk9/changes/jdk-9+167.html>. One change that maybe of interest is : * JEP 291: Deprecate the Concurrent Mark Sweep (CMS) Garbage Collector [1] * * *JDK 8u152 Early Access* build 03 is available at the new location : - jdk.java.net/8/ <http://jdk.java.net/8/> More information on the change of location for Early Access builds. [2] NOTE: - Oracle's JRE and JDK Cryptographic Roadmap has been updated since last availability email [3] Rgds,Rory [1] http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-April/005766.html [2] http://mail.openjdk.java.net/pipermail/adoption-discuss/2017-April/001610.h… [3] https://www.java.com/en/jre-jdk-cryptoroadmap.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (SLF4J-408) Incorrect module name for log4j-over-slf4j
by QOS.CH (JIRA) 27 Apr '17

27 Apr '17

[ https://jira.qos.ch/browse/SLF4J-408?page=com.atlassian.jira.plugin.system.… ] Stephen Colebourne commented on SLF4J-408: ------------------------------------------ Just to note that ideally the SLF4J jars we are talking about here should not be released until the ones they are replacing have locked down their module names. The log4j v1..x package name seems to be `org.apache.log4j`, so i assume that is what will get used - http://logging.apache.org/log4j/1.2/apidocs/index.html. > Incorrect module name for log4j-over-slf4j > ------------------------------------------ > > Key: SLF4J-408 > URL: https://jira.qos.ch/browse/SLF4J-408 > Project: SLF4J > Issue Type: Bug > Components: log4j-over-slf4j > Affects Versions: 1.8.0-alpha1 > Reporter: Stephen Colebourne > Assignee: SLF4J developers list > Fix For: 1.8.0-alpha2 > > > I need to write this exact use case up in more detail, but see the comments section of my [naming article|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] Basically, the module name must be the same for both the real log4j and the "fake" one being supplied by this artifact. > This is because the purpose of this module is to replace the log4j one, and because two packages cannot be in the same module. It is up to the build system, ie. Maven, to select the correct artifact to fulfill a given module name. > Based on discussions on the commons-dev mailing list, I'm proposing [these as the module names|http://mail-archives.apache.org/mod_mbox/commons-dev/201704.mbox/%3CC…] notably `org.apache.logging.log4j`. (This is based on my super-package reverse-DNS standard naming approach) > Thus the module-info.java file needs to change from a module name of `org.slf4j.log4j_over_slf4j` to `org.apache.logging.log4j`. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] bc0397: typo fix
by Ceki Gulcu 27 Apr '17

27 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: bc03976da8bc0b4e83bae3dc7404336e03e22017 https://github.com/qos-ch/slf4j/commit/bc03976da8bc0b4e83bae3dc7404336e03e2… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-27 (Thu, 27 Apr 2017) Changed paths: M slf4j-site/src/site/pages/news.html Log Message: ----------- typo fix

1 0

[qos-ch/slf4j] 4772ff: start work on 1.8.0-alpha3-SNAPSHOT
by Ceki Gulcu 27 Apr '17

27 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 4772fff68123c337e1b39de4ab8789faa8c98f1b https://github.com/qos-ch/slf4j/commit/4772fff68123c337e1b39de4ab8789faa8c9… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-27 (Thu, 27 Apr 2017) Changed paths: M integration/pom.xml M jcl-over-slf4j/pom.xml M jul-to-slf4j/pom.xml M log4j-over-slf4j/pom.xml M osgi-over-slf4j/pom.xml M pom.xml M slf4j-api/pom.xml M slf4j-ext/pom.xml M slf4j-jdk14/pom.xml M slf4j-log4j12/pom.xml M slf4j-migrator/pom.xml M slf4j-nop/pom.xml M slf4j-simple/pom.xml M slf4j-site/pom.xml Log Message: ----------- start work on 1.8.0-alpha3-SNAPSHOT

1 0

[JIRA] (SLF4J-407) Jigsaw modules contain clashing package
by QOS.CH (JIRA) 26 Apr '17

26 Apr '17

[ https://jira.qos.ch/browse/SLF4J-407?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü reopened SLF4J-407: ------------------------------ Assignee: Ceki Gülcü (was: SLF4J developers list) > Jigsaw modules contain clashing package > --------------------------------------- > > Key: SLF4J-407 > URL: https://jira.qos.ch/browse/SLF4J-407 > Project: SLF4J > Issue Type: Bug > Components: Implementations > Affects Versions: 1.8.0-alpha1 > Reporter: Stephen Colebourne > Assignee: Ceki Gülcü > Fix For: 1.8.0-alpha2 > > > Looking at the slf4j-jdk14 and slf4j-nop artifacts, they both appear to contain the package `org.slf4j.impl`. Jigsaw will refuse to load two modules that contain the same package, so this will be a problem. > I know that SLF4J does not intend users to load both of these modules at the same time. But the current setup means that it will be the JPMS runtime that rejects it, meaning that there is no chance for SLF4J to output a helpful message (as I believe it does today). > The solution to this would appear to be to move the `org.slf4j.impl` package to `org.slf4j.jul.impl` and `org.slf4j.nop.impl`. As the impl package is not exported, this should not affect any user code (except code that would have been affected anyway). > I imagine this affects other slf4j artifacts. > I also note that [this module-info.java|https://github.com/qos-ch/slf4j/blob/1_8_0-SNAPSHOT/slf4j-…] exports the `org.slf4j.jul` package, which seems unnecessary (simple and nop do not export their package). > See [here|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] for more information on naming. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-407) Jigsaw modules contain clashing package
by QOS.CH (JIRA) 26 Apr '17

26 Apr '17

[ https://jira.qos.ch/browse/SLF4J-407?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü commented on SLF4J-407: ---------------------------------- At present time, it seems that including org.slf4j.impl packages in order to cater for older versions of slf4j-api.jar in the class path seems worthwhile at the moment. By the way, I acknowledge your point about JPMS runtime rejecting multiple providers on the class path, leaving no opportunity to SLF4J to output a helpful message. I am somewhat conflicted about including org.slf4j.impl packages in slf4j providers and intend to revisit the issue in the near future. > Jigsaw modules contain clashing package > --------------------------------------- > > Key: SLF4J-407 > URL: https://jira.qos.ch/browse/SLF4J-407 > Project: SLF4J > Issue Type: Bug > Components: Implementations > Affects Versions: 1.8.0-alpha1 > Reporter: Stephen Colebourne > Assignee: SLF4J developers list > Fix For: 1.8.0-alpha2 > > > Looking at the slf4j-jdk14 and slf4j-nop artifacts, they both appear to contain the package `org.slf4j.impl`. Jigsaw will refuse to load two modules that contain the same package, so this will be a problem. > I know that SLF4J does not intend users to load both of these modules at the same time. But the current setup means that it will be the JPMS runtime that rejects it, meaning that there is no chance for SLF4J to output a helpful message (as I believe it does today). > The solution to this would appear to be to move the `org.slf4j.impl` package to `org.slf4j.jul.impl` and `org.slf4j.nop.impl`. As the impl package is not exported, this should not affect any user code (except code that would have been affected anyway). > I imagine this affects other slf4j artifacts. > I also note that [this module-info.java|https://github.com/qos-ch/slf4j/blob/1_8_0-SNAPSHOT/slf4j-…] exports the `org.slf4j.jul` package, which seems unnecessary (simple and nop do not export their package). > See [here|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] for more information on naming. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j]
by ceki 25 Apr '17

25 Apr '17

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

1 0

[JIRA] (SLF4J-407) Jigsaw modules contain clashing package
by QOS.CH (JIRA) 25 Apr '17

25 Apr '17

[ https://jira.qos.ch/browse/SLF4J-407?page=com.atlassian.jira.plugin.system.… ] Ceki Gülcü resolved SLF4J-407. ------------------------------ Resolution: Fixed > Jigsaw modules contain clashing package > --------------------------------------- > > Key: SLF4J-407 > URL: https://jira.qos.ch/browse/SLF4J-407 > Project: SLF4J > Issue Type: Bug > Components: Implementations > Affects Versions: 1.8.0-alpha1 > Reporter: Stephen Colebourne > Assignee: SLF4J developers list > Fix For: 1.8.0-alpha2 > > > Looking at the slf4j-jdk14 and slf4j-nop artifacts, they both appear to contain the package `org.slf4j.impl`. Jigsaw will refuse to load two modules that contain the same package, so this will be a problem. > I know that SLF4J does not intend users to load both of these modules at the same time. But the current setup means that it will be the JPMS runtime that rejects it, meaning that there is no chance for SLF4J to output a helpful message (as I believe it does today). > The solution to this would appear to be to move the `org.slf4j.impl` package to `org.slf4j.jul.impl` and `org.slf4j.nop.impl`. As the impl package is not exported, this should not affect any user code (except code that would have been affected anyway). > I imagine this affects other slf4j artifacts. > I also note that [this module-info.java|https://github.com/qos-ch/slf4j/blob/1_8_0-SNAPSHOT/slf4j-…] exports the `org.slf4j.jul` package, which seems unnecessary (simple and nop do not export their package). > See [here|http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html] for more information on naming. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/slf4j] 70ec42: prepare release 1.8.0-alpha2
by Ceki Gulcu 25 Apr '17

25 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 70ec42263abf188950cd2a8f8eb4502c9c372ac1 https://github.com/qos-ch/slf4j/commit/70ec42263abf188950cd2a8f8eb4502c9c37… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-26 (Wed, 26 Apr 2017) Changed paths: M integration/pom.xml M jcl-over-slf4j/pom.xml M jul-to-slf4j/pom.xml M log4j-over-slf4j/pom.xml M osgi-over-slf4j/pom.xml M pom.xml M slf4j-api/pom.xml M slf4j-ext/pom.xml M slf4j-jdk14/pom.xml M slf4j-log4j12/pom.xml M slf4j-migrator/pom.xml M slf4j-nop/pom.xml M slf4j-simple/pom.xml M slf4j-site/pom.xml M slf4j-site/src/site/pages/codes.html Log Message: ----------- prepare release 1.8.0-alpha2

1 0