[slf4j-dev] [JIRA] (SLF4J-428) automatic module name for jul-to-slf4j contains illegal token

[QOS.CH (JIRA)]

    [ https://jira.qos.ch/browse/SLF4J-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19379#comment-19379 ] 

Gili commented on SLF4J-428:
----------------------------

Ceki,

The JDK 11 implementation lines up with my interpretation of the specification.

I went one step further. I downloaded the latest version of JDK 9 from [https://jdk.java.net/archive/] (version 9.0.4) and it compiled just fine against both the testcase and jul.to.slf4j.

So, are we able to put back the module name to *jul.to.slf4j*?

> 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
>
>         Attachments: jpms-testcase.zip
>
>
> the automatic module name that is created in Java 9 for the jul-to-slf4 jar is _jul.to.slf4j at 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)