[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.i... ] Anders Kreinøe commented on SLF4J-124: -------------------------------------- Are there other places where java 8 would be helpfull? If this is the main reason for Java 8, then I still think is a bad idea, as there is a fine way to implement it, working from java 5 and up. Looking at the backends, newest version of log4j (2.7) requires only java 7, and not long ago (version 2.3) it only required java 6. Logback seems to still support java 6. I cannot say anything about how big a part of new project is based on older java versions, but I now they are not uncommon. It pretty typical for enterprise organazations (or at leas i know of some) to hang on to older versions of java, both by practical but also political reasons. So overall I would think its a bad idea to make slf4j require java 8 at this time. Also breaking the Logger interface would break end user code for some users, as there is end users that has implemented there own Logger classes for different reasons.

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