[jira] [Created] (LOG4J2-3476) Support JUL ApiLogger::setLevel

["Remko Popma (Jira)" <ji...@apache.org>]

Remko Popma created LOG4J2-3476:
-----------------------------------

             Summary: Support JUL ApiLogger::setLevel
                 Key: LOG4J2-3476
                 URL: https://issues.apache.org/jira/browse/LOG4J2-3476
             Project: Log4j 2
          Issue Type: New Feature
          Components: JUL adapter
    Affects Versions: 2.17.2
            Reporter: Remko Popma
            Assignee: Remko Popma
             Fix For: 2.17.3


The current implementation of ApiLogger::setLevel is to throw an UnsupportedOperation Exception.

It turns out that Gradle's internal logging tries to call this method under some configurations, and it cannot deal gracefully with that Exception, so the build fails.

[~mattsicker] I was wondering if there is any reason why the implementation could not be like this:

{code}
@Override
public void setLevel(final Level newLevel) throws SecurityException {
    doSetLevel(newLevel);
    Configurator.setLevel(logger, LevelTranslator.toLevel(newLevel));
}
{code}

I will try this in a test project.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)