- slf4j-dev - mailman3.qos.ch

Tentative release date for 1.8?
by Nandimandalam, Varun 25 Jun '18

25 Jun '18

To maintainers, I am looking for slf4j prod version that has support for Java 9 modules. As only 1.8.0-beta is modularized, do you have a tentative release date for 1.8.0 prod release? If its farther out in the year, how safe it is to use the beta version? Thank you, Varun

1 0

[JIRA] (SLF4J-420) Make a release with Automatic-Module-Name
by QOS.CH (JIRA) 18 Jun '18

18 Jun '18

[ https://jira.qos.ch/browse/SLF4J-420?page=com.atlassian.jira.plugin.system.… ] Varun Nandi commented on SLF4J-420: ----------------------------------- @ceki Any updates on this issue? If you can create a branch for 1.7.26, I can send a PR. Thanks. > Make a release with Automatic-Module-Name > ----------------------------------------- > > Key: SLF4J-420 > URL: https://jira.qos.ch/browse/SLF4J-420 > Project: SLF4J > Issue Type: Task > Reporter: Gael Lalire > Assignee: Ceki Gülcü > Priority: Trivial > Fix For: 1.7.26 > > > You can make a release with Automatic-Module-Name with 1.7 version so it can load logback and have the package name you choose in 1.8 beta. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Re: [slf4j-dev] Adding Automatic-Module-Name to 1.7.x
by Nandimandalam, Varun 08 Jun '18

08 Jun '18

Ping. Is this the right email list to reach out to repo maintainers? From: slf4j-dev <slf4j-dev-bounces(a)qos.ch> on behalf of "Nandimandalam, Varun" <varunkn(a)amazon.com> Reply-To: slf4j developers list <slf4j-dev(a)qos.ch> Date: Monday, June 4, 2018 at 11:06 AM To: "slf4j-dev(a)qos.ch" <slf4j-dev(a)qos.ch> Subject: [slf4j-dev] Adding Automatic-Module-Name to 1.7.x Hi, I want to know if there are any plans on adding Automatic-Module-Name to 1.7.x so that other Java 9 compatible libraries can depend of slf4j. I noticed it has been added to few modules in 1.8 but this version is still in beta. There is an open PR (https://github.com/qos-ch/slf4j/pull/184) to address this issue but the repo maintainers need to create a branch first before outside developers can send PRs. Our library is moving to JPMS and is depending on 1.7.x, it would be helpful if you can add Automatic-Module-Name and release 1.7.26 version. Thank you, Varun

1 0

[JIRA] (SLF4J-418) Add JSR 305 to SLF4j
by QOS.CH (JIRA) 05 Jun '18

05 Jun '18

[ https://jira.qos.ch/browse/SLF4J-418?page=com.atlassian.jira.plugin.system.… ] Sebastian Davids commented on SLF4J-418: ---------------------------------------- Guava is not using jsr305 anymore: https://github.com/google/guava/issues/2960 > Add JSR 305 to SLF4j > -------------------- > > Key: SLF4J-418 > URL: https://jira.qos.ch/browse/SLF4J-418 > Project: SLF4J > Issue Type: Bug > Components: Core API > Affects Versions: 2.0, 1.8.0-alpha2 > Reporter: Erik Pragt > Assignee: SLF4J developers list > Labels: kotlin > > A few years ago, attempts have been made to implement JSR 305 in SLF4j. This was rolled back due to a Scala compiler issue, which, 5 years later, still hasn't been fixed. In the meantime, other libraries, like Guava, most of Square's libraries ([https://medium.com/square-corner-blog/rolling-out-nullable-42dd823fbd89) the Spring framework, etc, have implemented JSR 305. JSR 305 is now supported by tools like Findbugs, and languages like Kotlin, and IDEs like Eclipse and IntelliJ make use of this meta information to detect bugs. > I hope that by now, we can also add JSR 305 information into SLF4j. If the Scala issue is still an issue, it seems that this issue should either be fixed by Lightbend, or they will run into issues with other frameworks anyway. Anyhow, IMO, it seems the Scala compiler should not be a reason to withhold this change from happening. > The main motivation is that it will make programming in Kotlin easier (right now, types from SLF4j are platform types, and the compiler has no information if this is a nullable or non-nullable type, making SLF4j harder to use), but, as a side effect, it will help IDEs and other tooling. > > -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

Adding Automatic-Module-Name to 1.7.x
by Nandimandalam, Varun 04 Jun '18

04 Jun '18

Hi, I want to know if there are any plans on adding Automatic-Module-Name to 1.7.x so that other Java 9 compatible libraries can depend of slf4j. I noticed it has been added to few modules in 1.8 but this version is still in beta. There is an open PR (https://github.com/qos-ch/slf4j/pull/184) to address this issue but the repo maintainers need to create a branch first before outside developers can send PRs. Our library is moving to JPMS and is depending on 1.7.x, it would be helpful if you can add Automatic-Module-Name and release 1.7.26 version. Thank you, Varun

1 0

JDK 11 Early Access build 15 is available for download.
by Rory O'Donnell 29 May '18

29 May '18

Hi Ceki, **JDK 11 EA build 15 , *****under both the GPL and Oracle EA licenses, is now available at **http://jdk.java.net/11**. ** * * Newly approved 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 http://jdk.java.net/11/changes *Notable changes in JDK 11 EA builds since last email:* * b15 - JDK-8201627 <http://bugs.openjdk.java.net/browse/JDK-8201627> - Kerberos sequence number issues * b13 - JDK-8200146 <http://bugs.openjdk.java.net/browse/JDK-8200146> - Removal of appletviewer launcher o deprecated in JDK 9 and has been removed in this release * b13 - JDK-8201793 <http://bugs.openjdk.java.net/browse/JDK-8201793> - java.lang.ref.Reference does not support cloning ** ** JEPs proposed to target JDK 11 (review ends 2018/05/31 23:00 UTC) 330: Launch Single-File Source-Code Programs <http://openjdk.java.net/jeps/330> JEPs targeted to JDK 11, so far 309: Dynamic Class-File Constants <http://openjdk.java.net/jeps/309> 318: Epsilon: A No-Op Garbage Collector <http://openjdk.java.net/jeps/318> 320: Remove the Java EE and CORBA Modules <http://openjdk.java.net/jeps/320> 321: HTTP Client (Standard) <http://openjdk.java.net/jeps/321> 323: Local-Variable Syntax for Lambda Parameters <http://openjdk.java.net/jeps/323> 324: Key Agreement with Curve25519 and Curve448 <http://openjdk.java.net/jeps/324> 327: Unicode 10 <http://openjdk.java.net/jeps/327> 328: Flight Recorder <http://openjdk.java.net/jeps/328> 329: ChaCha20 and Poly1305 Cryptographic Algorithms <http://openjdk.java.net/jeps/329> Finally, Initial TLSv1.3 implementation Released to the Open Sandbox. Please note well: this branch is under very active development and is not final by any means. Also note: by releasing this code, we are not committing a specific release or timeframe. We will continue development and fixing bugs until the code is ready for inclusion in the JDK. We welcome your feedback, more info [1] Regards, Rory [1] http://mail.openjdk.java.net/pipermail/security-dev/2018-May/017139.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin,Ireland

1 0

[JIRA] (SLF4J-437) Create a BOM POM
by QOS.CH (JIRA) 23 May '18

23 May '18

Michael Osipov created SLF4J-437: ------------------------------------ Summary: Create a BOM POM Key: SLF4J-437 URL: https://jira.qos.ch/browse/SLF4J-437 Project: SLF4J Issue Type: Task Affects Versions: 1.8.0-beta2 Reporter: Michael Osipov Assignee: SLF4J developers list Please create a {{slf4j-bom}} POM which can be imported via dependency management. This makes consumer POM less verbose, no need to repeat version. The Spring Framework does this for example. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-412) Missing export in manifest file
by QOS.CH (JIRA) 18 May '18

18 May '18

[ https://jira.qos.ch/browse/SLF4J-412?page=com.atlassian.jira.plugin.system.… ] Björn Kautler commented on SLF4J-412: ------------------------------------- I don't think that export was corret, as there were no classes in that package in this bundle. This export was removed when the OSGi Log Service specification was properly implemented in 1.7.14. If you get the missing dependency message, then I suspect it is exactly that, you have no bundle deployed that provides the OSGi log service. So either add a bundle that provides the log service or remove this bundle from your configuration. For me in my little test project the log service is provided by the bundle {{org.apache.felix.gogo.command}}. All the popular OSGi containers should provide an implementation as you can see at [https://en.wikipedia.org/wiki/OSGi_Specification_Implementations#101:_Log_S…] > Missing export in manifest file > ------------------------------- > > Key: SLF4J-412 > URL: https://jira.qos.ch/browse/SLF4J-412 > Project: SLF4J > Issue Type: Bug > Components: osgi-over-slf4j > Affects Versions: 1.7.14, 1.7.25 > Reporter: Herve Dumont > Assignee: SLF4J developers list > > Issue is a regression from SLF4J-341. > version 1.7.13 was exporting org.osgi.service.log > starting v 1.7.14 org.osgi.service.log is not longer exported,. > bundle cannot be started due missing dependency org.osgi.service.log. > Adding > Export-Package: org.osgi.service.log;uses:="org.osgi.framework";version="1.3" > should solve the issue -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (SLF4J-434) Suggestion: Additional simplelogger.properties file
by QOS.CH (JIRA) 16 May '18

16 May '18

[ https://jira.qos.ch/browse/SLF4J-434?page=com.atlassian.jira.plugin.system.… ] Joachim Durchholz commented on SLF4J-434: ----------------------------------------- This can be cancelled. I could make my use case expire, because it was easier to get an okay from my superiors to do the work to switch to logback, than to obtain even a documentation PR review from Ceki. > Suggestion: Additional simplelogger.properties file > --------------------------------------------------- > > Key: SLF4J-434 > URL: https://jira.qos.ch/browse/SLF4J-434 > Project: SLF4J > Issue Type: Improvement > Reporter: Joachim Durchholz > Assignee: SLF4J developers list > Priority: Minor > > Allow an additional simplelogger.properties file. > Use case: We have a simplelogger.properties in the git-managed source tree. However, we also want to have a .gitignored properties file so we can do quick local testing. > Suggestion: > Add configuration directive org.slf4j.simpleLogger.configFile. > Includes the file, overriding the settings from the source that the configFile directive was in (simplelogger.properties or system properties, whichever may be the case). > The included file must not contain another configFile directive. > My status: Discussion welcome. Willing to contribute patch if so desired. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 11 Early Access build 12 available
by Rory O'Donnell 08 May '18

08 May '18

Hi Ceki, **JDK 11 EA build 12 , *****under both the GPL and Oracle EA licenses, is now available at **http://jdk.java.net/11**. ** * * Newly approved 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/12/jdk-11+12.html *Notable changes in JDK 11 EA builds since last email:* * Build 11 - see Release Notes for details. o JDK-8201315 : SelectableChannel.register may be invoked while a selection operation is in progress * Build 10 - see Release Notes for details. o JDK-8200149 : Removal of "com.sun.awt.AWTUtilities" class o JDK-8189997 (not public) : Enhanced KeyStore Mechanisms o JDK-8175075 (not public) : 3DES Cipher Suites Disabled * Build 9: - see Release Notes for details. o JDK-8200152 : KerberosString uses UTF-8 encoding by default o JDK-8200458 : Readiness information previously recorded in SelectionKey ready set not preserved ** *Draft JEP: Deprecate pack200, unpack200 tools and related APIs. [1] * This draft JEP [2] proposes to deprecate the pack200 APIs and tools in the JDK. As outlined in the JEP, the usefulness of this technology have diminishing returns, the components using them are being removed and connectivity speeds have improved by leaps and bounds, since its inception. Feedback appreciated via http://mail.openjdk.java.net/pipermail/jdk-dev Regards, Rory [1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-April/001074.html [2] https://bugs.openjdk.java.net/browse/JDK-8200752 Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin,Ireland

1 0