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

[JIRA] (SLF4J-438) IllegalAccessError in MDC when using Java 10
by QOS.CH (JIRA) 27 Jun '18

27 Jun '18

Andreas Bergander created SLF4J-438: --------------------------------------- Summary: IllegalAccessError in MDC when using Java 10 Key: SLF4J-438 URL: https://jira.qos.ch/browse/SLF4J-438 Project: SLF4J Issue Type: Bug Affects Versions: 1.7.25 Environment: Java 10 slf4j-api-1.7.25 slf4j-log4j12-1.7.25 Reporter: Andreas Bergander Assignee: SLF4J developers list When using MDC and log4j I get an IllegalAccessError during initialization. {noformat} java.lang.IllegalAccessError: tried to access field org.apache.log4j.MDC.mdc from class org.apache.log4j.MDCFriend at org.apache.log4j.MDCFriend.fixForJava9(MDCFriend.java:11) at org.slf4j.impl.Log4jMDCAdapter.<clinit>(Log4jMDCAdapter.java:38) at org.slf4j.impl.StaticMDCBinder.getMDCA(StaticMDCBinder.java:59) at org.slf4j.MDC.bwCompatibleGetMDCAdapterFromBinder(MDC.java:99) at org.slf4j.MDC.<clinit>(MDC.java:108) {noformat} I guess package private fields are not accessible between different jar-files anymore in Java 10. Or am I doing something wrong? -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

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