- slf4j-dev - mailman3.qos.ch

[qos-ch/slf4j] 685d05: site update
by Ceki Gulcu 07 Apr '17

07 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 685d0598cd47c6cc23ad655e60322a7583b959af https://github.com/qos-ch/slf4j/commit/685d0598cd47c6cc23ad655e60322a7583b9… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-07 (Fri, 07 Apr 2017) Changed paths: M pom.xml M slf4j-site/src/site/pages/download.html M slf4j-site/src/site/pages/faq.html M slf4j-site/src/site/pages/news.html M slf4j-site/src/site/pages/templates/left.js Log Message: ----------- site update

1 0

Release of SLF4J version 1.8.0-alpha0
by Ceki Gulcu 07 Apr '17

07 Apr '17

Java 9 modularization ===================== I am pleased to announce SLF4J 1.8.0-alpha0, a modularized version of slf4j compatible with Java 9 and in particular its Java Platform Module System (JSR 376), a.k.a project Jigsaw. Although there are no client facing API changes in 1.8.0-alpha0 release, the static binding mechanism has been abandoned in favor of java.util.ServiceLoader introduced in Java 6. It follows that slf4j-api now requires Java 6. Just as importantly, slf4j-api version 1.8.x will no longer search for the StaticLoggerBinder class. Instead of "bindings" now slf4j-api looks for "providers" which ship with slf4j-nop-1.8.x.jar, slf4j-simple-1.8.x.jar or slf4j-jdk14-1.8.x.jar. Given that in some environments, it is not possible to modify the version of slf4j-api, slf4j 1.8.x "providers" also act as 1.7.x/1.6.x "bindings". For example, having slf4j-api-1.8.x.jar and slf4j-simple-1.7.x.jar on the class path will NOT work, whereas having slf4j-api-1.7.x.jar and slf4j-simple-1.8.x.jar on the class path will work fine. In other words: slf4j-api-1.8.x.jar + slf4j-simple-1.7.x.jar ==> "No SLF4J providers found" warning whereas: slf4j-api-1.7.x.jar + slf4j-simple-1.8.x.jar ==> OK Download ======== The relevant artifacts can be obtained via the Maven central repository. OSGi changes ============ While we expect the changes introduced in SLF4J 1.8.x to be rather transparent to users, given JPMS restrictions, implementations had to be moved from the org.slf4.impl package to packages specific to each provider. Consequently, the OSGi declarations in MANIFEST.MF files had to be modified. Our tests indicate that SLF4J version 1.8.x should work fine with OSGi. However, more in depth testing is in order. We are looking for volunteers for such tests. The slf4j-log4j12 module ======================== Due to technical reasons, slf4j-log4j12 could not be modularized in this alpha0 release. However, we expect the problem to be solved in future 1.8.x releases. Announcement mailing list ========================= You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

JDK 9 Developer Preview is now available on java.net
by Rory O'Donnell 07 Apr '17

07 Apr '17

Hi Ceki, *JDK 9 Developer Preview is now available on java.net [1] * Developer Preview milestone: - A reasonably stable build suitable for broad testing by the developer community is available. JDK 9 Builds 163 and higher include all planned features. *Attention annotation processing users and authors - * Request for feedback on annotation processing API changes made in JDK 9. As has been done previously during Java SE 7 and Java SE 8, the JSR 269 annotation processing API is undergoing a maintenance review (MR) as part of Java SE 9. Details of the changes in JDK 9 Early Access build 163 & build 164 available here [2] Please report experiences running processors under JDK 9 and feedback on the API changes to the compiler-dev mailing list. (If you haven’t already subscribed to that list then please do so first, otherwise your message will be discarded as spam.) Rgds, Rory [1] https://jdk9.java.net/download/ [2] http://mail.openjdk.java.net/pipermail/compiler-dev/2017-April/010896.html -- Rgds,Rory O'Donnell Quality Engineering Manager

1 0

[qos-ch/slf4j] 541e6f: update maven site-plugin to 3.6
by Ceki Gulcu 07 Apr '17

07 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 541e6f7d181ff3405ae9495724430825aefff6a9 https://github.com/qos-ch/slf4j/commit/541e6f7d181ff3405ae9495724430825aeff… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-07 (Fri, 07 Apr 2017) Changed paths: M pom.xml Log Message: ----------- update maven site-plugin to 3.6

1 0

[qos-ch/slf4j] 578cce: better luck with default java 9 toolchain
by Ceki Gulcu 07 Apr '17

07 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: 578cce94f755c6f53c72b661d9ffbd89111279d3 https://github.com/qos-ch/slf4j/commit/578cce94f755c6f53c72b661d9ffbd891112… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-07 (Fri, 07 Apr 2017) Changed paths: M pom.xml Log Message: ----------- better luck with default java 9 toolchain

1 0

[qos-ch/slf4j] ef31ab: attempt release 1.8.0-alpha0
by Ceki Gulcu 07 Apr '17

07 Apr '17

Branch: refs/heads/1_8_0-SNAPSHOT Home: https://github.com/qos-ch/slf4j Commit: ef31abdd138fe7cdd0a8ef8370bfcc8e3f7325b9 https://github.com/qos-ch/slf4j/commit/ef31abdd138fe7cdd0a8ef8370bfcc8e3f73… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-04-07 (Fri, 07 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: ----------- attempt release 1.8.0-alpha0

1 0

[JIRA] (SLF4J-328) Binding Ambiguity check skipped for Andriod
by QOS.CH (JIRA) 07 Apr '17

07 Apr '17

[ https://jira.qos.ch/browse/SLF4J-328?page=com.atlassian.jira.plugin.system.… ] Lin Wang commented on SLF4J-328: -------------------------------- Never mind, my bad, I used to have the following line to exclude a transitive dependency on slf4j-api in my gradle file since slf4j-api was built into slf4j-android 1.6.1-RC1. *configurations.all*.exclude module: 'slf4j-api'* After removing that line, I can successfully compile slf4j-android:1.7.25 now, since slf4j-android:1.7.x doesn't include the slf4j-api directly anymore. > Binding Ambiguity check skipped for Andriod > ------------------------------------------- > > Key: SLF4J-328 > URL: https://jira.qos.ch/browse/SLF4J-328 > Project: SLF4J > Issue Type: Improvement > Components: Core API > Affects Versions: 1.7.x > Environment: Android > Reporter: Nitin Verma > Assignee: Ceki Gülcü > Priority: Critical > Fix For: 1.7.14 > > Attachments: FindStaticLoggerBinderPathsPerfTest.java > > > https://github.com/nitinverma/slf4j/commit/4d67b578fdc1cf77a0689f2efb0424f6… > As Dex cant by design have duplicate class, there would never be a 'Binding Ambiguity'. > 1. LoggerFactory.getLogger is mostly called via MainActivity. Which gives a black screen before the first activity loads. > 2. This operation takes 200-600 Inclusive CPU Time as per DDMS. > This fix get Incl CPU Time to sub 10 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-328) Binding Ambiguity check skipped for Andriod
by QOS.CH (JIRA) 05 Apr '17

05 Apr '17

[ https://jira.qos.ch/browse/SLF4J-328?page=com.atlassian.jira.plugin.system.… ] Lin Wang commented on SLF4J-328: -------------------------------- Thanks, I tried to pick up the latest version for my android application but keep having this compilation errors: Please advise. {code:java} error: package org.slf4j does not exist import org.slf4j.Logger;{code} buildscript \{ repositories \{ mavenCentral() maven \{ url "https://mvnrepository.com/artifact/org.slf4j/slf4j-android" } maven \{ url "https://mvnrepository.com/artifact/org.slf4j/slf4j-api" } } } dependencies \{ // compile 'org.slf4j:slf4j-android:1.6.1-RC1' compile 'org.slf4j:slf4j-api:1.7.25' compile 'org.slf4j:slf4j-android:1.7.25' } > Binding Ambiguity check skipped for Andriod > ------------------------------------------- > > Key: SLF4J-328 > URL: https://jira.qos.ch/browse/SLF4J-328 > Project: SLF4J > Issue Type: Improvement > Components: Core API > Affects Versions: 1.7.x > Environment: Android > Reporter: Nitin Verma > Assignee: Ceki Gülcü > Priority: Critical > Fix For: 1.7.14 > > Attachments: FindStaticLoggerBinderPathsPerfTest.java > > > https://github.com/nitinverma/slf4j/commit/4d67b578fdc1cf77a0689f2efb0424f6… > As Dex cant by design have duplicate class, there would never be a 'Binding Ambiguity'. > 1. LoggerFactory.getLogger is mostly called via MainActivity. Which gives a black screen before the first activity loads. > 2. This operation takes 200-600 Inclusive CPU Time as per DDMS. > This fix get Incl CPU Time to sub 10 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-328) Binding Ambiguity check skipped for Andriod
by QOS.CH (JIRA) 05 Apr '17

05 Apr '17

[ https://jira.qos.ch/browse/SLF4J-328?page=com.atlassian.jira.plugin.system.… ] Nitin Verma commented on SLF4J-328: ----------------------------------- yes. it is in master. starting tag v_1.7.14 (https://github.com/qos-ch/slf4j/releases/tag/v_1.7.14) https://github.com/qos-ch/slf4j/commit/fc0ad8652b8485175a6295648c05425284b8… > Binding Ambiguity check skipped for Andriod > ------------------------------------------- > > Key: SLF4J-328 > URL: https://jira.qos.ch/browse/SLF4J-328 > Project: SLF4J > Issue Type: Improvement > Components: Core API > Affects Versions: 1.7.x > Environment: Android > Reporter: Nitin Verma > Assignee: Ceki Gülcü > Priority: Critical > Fix For: 1.7.14 > > Attachments: FindStaticLoggerBinderPathsPerfTest.java > > > https://github.com/nitinverma/slf4j/commit/4d67b578fdc1cf77a0689f2efb0424f6… > As Dex cant by design have duplicate class, there would never be a 'Binding Ambiguity'. > 1. LoggerFactory.getLogger is mostly called via MainActivity. Which gives a black screen before the first activity loads. > 2. This operation takes 200-600 Inclusive CPU Time as per DDMS. > This fix get Incl CPU Time to sub 10 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-328) Binding Ambiguity check skipped for Andriod
by QOS.CH (JIRA) 05 Apr '17

05 Apr '17

[ https://jira.qos.ch/browse/SLF4J-328?page=com.atlassian.jira.plugin.system.… ] Lin Wang commented on SLF4J-328: -------------------------------- Is this also fixed in the [https://www.slf4j.org/android/] distributions? We are currently using the 'org.slf4j:slf4j-android:1.6.1-RC1' along with 'org.apache.thrift:libthrift:0.9.2' and we are still seeing this slow ClassLoader.getResources() issue which even takes 225ms on a powerful Samsung S6 device. > Binding Ambiguity check skipped for Andriod > ------------------------------------------- > > Key: SLF4J-328 > URL: https://jira.qos.ch/browse/SLF4J-328 > Project: SLF4J > Issue Type: Improvement > Components: Core API > Affects Versions: 1.7.x > Environment: Android > Reporter: Nitin Verma > Assignee: Ceki Gülcü > Priority: Critical > Fix For: 1.7.14 > > Attachments: FindStaticLoggerBinderPathsPerfTest.java > > > https://github.com/nitinverma/slf4j/commit/4d67b578fdc1cf77a0689f2efb0424f6… > As Dex cant by design have duplicate class, there would never be a 'Binding Ambiguity'. > 1. LoggerFactory.getLogger is mostly called via MainActivity. Which gives a black screen before the first activity loads. > 2. This operation takes 200-600 Inclusive CPU Time as per DDMS. > This fix get Incl CPU Time to sub 10 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0