[ https://jira.qos.ch/browse/SLF4J-124?page=com.atlassian.jira.plugin.system.i... ] Ralph Goers commented on SLF4J-124: ----------------------------------- I am not sure what the big deal is here with implementing this. The Log4j 2 API has supported this since 2013. So we would have no trouble adding support for the new methods required for this, unless they do something truly bizarre. I suppose another way to solve this is for user's to use the Log4j 2 API and then use log4j-to-slf4j to route back to SLF4J.
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 (v7.3.1#73012)