[slf4j-dev] [JIRA] (SLF4J-401) Upgrade SLF4J binding mechanism to use java.util.ServiceLoader

[QOS.CH (JIRA)]

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

Patrick Reinhart commented on SLF4J-401:
----------------------------------------

The additional `module-info.class` in the root of the JAR want be a problem for an pre JDK 9 because it's not used there anyway. 

If you wanted to use JDK 9 specific stuff for let's say performance improvements, then a multi release JAR comes into play. There you can overwrite/add some classes using the JDK 9 specific stuff and put them into the same JAR. If that is not needed at the moment we do not need a multi release JAR at all.

> Upgrade SLF4J binding mechanism to use java.util.ServiceLoader
> --------------------------------------------------------------
>
>                 Key: SLF4J-401
>                 URL: https://jira.qos.ch/browse/SLF4J-401
>             Project: SLF4J
>          Issue Type: Sub-task
>          Components: Core API
>            Reporter: Ceki Gülcü
>            Assignee: Ceki Gülcü
>            Priority: Blocker
>              Labels: binding
>             Fix For: 1.8.0
>
>
> The {{org.slf4j.impl.StaticXYZBinder}} approach has been surprisingly successful for such a crude mechanism. However, with the advent of Java 9/jigsaw/modularisation we need a more standard approach. {{java.util.ServiceLoader}} introduced in Java 6 seems to fit the bill.



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