[LOG4J2-3476] Support JUL ApiLogger::setLevel

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.17.2
• Fix Version/s: 2.18.0
• Component/s: JUL adapter
• Assignee: Remko Popma
• Reporter: Remko Popma
• Created: 13/Apr/22 09:26
• Updated: 02/May/22 21:13
• Resolved: 02/May/22 21:13

Description

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:

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

I will try this in a test project.

(5 minutes later...) Looking at LOG4J2-1110, I understand that this can be done in CoreLogger but not in ApiLogger.

Still, would it be possible to silently ignore this call to setLevel, rather than throwing an UnsupportedOperationException?

Issue Links

• relates to: LOG4J2-1110 org.apache.logging.log4j.jul.CoreLogger.setLevel() checks for security permission too late
• links to: GitHub Pull Request #821