[ https://jira.qos.ch/browse/SLF4J-428?page=com.atlassian.jira.plugin.system.i... ] Rob Platt commented on SLF4J-428: --------------------------------- Hi Ceki. Would it be possible to get out 1.8.0-beta2 with the already fixed issues in it, and move the open issues to a beta3? Seems like there is quite some work remaining in the release, but this particular fix makes a really big difference when modularizing a project. We could create our own internal package, and will if it comes to it, but I thought there was no harm in asking in case others in the community are looking forward to this fix too :)

automatic module name for jul-to-slf4j contains illegal token -------------------------------------------------------------

Key: SLF4J-428 URL: https://jira.qos.ch/browse/SLF4J-428 Project: SLF4J Issue Type: Bug Components: jul-to-slf4j Affects Versions: 1.8.0-beta1 Reporter: Peter-Josef Meisch Assignee: Ceki Gülcü Fix For: 1.8.0-beta2

the automatic module name that is created in Java 9 for the jul-to-slf4 jar is _jul.to.slf4j@1.8.0-beta1_. This contains the token *to* which is a reserved word in Java 9 so the generated name cannot be used in requires statements in modul-info.java files of projects using jul-to-slf4j and inhibits migration of projects to Java 9. This should be modified by adding {{Automatic-Module-Name: jul_to_slf4j}} to the manifest for the archive.

-- This message was sent by Atlassian JIRA (v7.3.1#73012)