[ https://jira.qos.ch/browse/SLF4J-428?page=com.atlassian.jira.plugin.system.i... ] Gili commented on SLF4J-428: ---------------------------- Wait, having re-read [https://stackoverflow.com/a/36322692/14731] I don't see why you guys are having a problem. Highlighting the relevant bits: {quote}These character sequences are tokenized as keywords *solely where they appear as terminals* in the ModuleDeclaration and ModuleDirective productions (§7.7). {quote} Per my understanding, you don't need to use *to* as a terminal. It is in the middle of your ModuleDeclaration. Further, I created a sample project under Java 11 and I can't get a compiler error using "to" no matter what I do. I will try attaching it to this issue for your review.
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, 1.8.0-beta3
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)