[slf4j-dev] [JIRA] (SLF4J-420) Make a release with Automatic-Module-Name

[QOS.CH (JIRA)]

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

Varun Nandi commented on SLF4J-420:
-----------------------------------

Hi,

Any updates? Can you atleast let us know when you are planning to GA a version that is compatible with Java 9 module system.
Our GA is blocked by this issue. If we depend on 1.7.26, the module name is derived from the jar. Then if you change the module name in 1.8, all our customers will be broken. I see following 2 options:

1) Release a GA version of 1.8.x with Java module info

2) Release a patch version on top of 1.7.26 with "Automatic-Module-Name" in the manifest

See this article for better understanding of the issue:

[https://dzone.com/articles/automatic-module-name-calling-all-java-library-maintainers]

 

Thank you

> 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)