[slf4j-dev] [JIRA] (SLF4J-124) Add ability to log at a dynamic level

[QOS.CH (JIRA)]

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

Ceki Gulcu commented on SLF4J-124:
----------------------------------

I'd like to move to JDK 8 for SLF4J 2.0. However, AFAIK 50% of the Java users are still on JDK 7 or older.

Default methods in interfaces are really awesome. My primary concern is to avoid breaking end-user code. Implementors of the Logger interface is less of a concern. The latter are just a handful whereas the former are in the millions. Having said this, I don't think adding methods to the Logger interface will break client code. Nevertheless, I agree that keeping backward compatibility for implementors is nice (but not crucial).

You can have lamda support without requiring Java 8. See my email with the subject [Lambda support in SLF4J|http://mailman.qos.ch/pipermail/slf4j-dev/2016-December/004593.html].

As for end of public updates for JDK 7, as mentioned above, there are many projects still using JDK 7. I guess new projects are on JDK 8 though.





> Add ability to log at a dynamic level
> -------------------------------------
>
>                 Key: SLF4J-124
>                 URL: https://jira.qos.ch/browse/SLF4J-124
>             Project: SLF4J
>          Issue Type: Sub-task
>          Components: Core API
>    Affects Versions: 1.5.x
>         Environment: Operating System: All
> Platform: All
> URL: http://stackoverflow.com/questions/2621701/setting-log-level-of-message-at-runtime-in-slf4j
>            Reporter: Robert Elliot
>            Assignee: SLF4J developers list
>         Attachments: Util.java.patch
>
>
> It is occasionally useful to have a log method that takes a level as a parameter.  The necessary methods can be added to the Util class without any compatibility issues as far as I can see - see attached patch.



--
This message was sent by Atlassian JIRA
(v6.4.12#64027)