JetBrains IntelliJ Platform Drops Log4j in Favor of java.util.logging – Migration Guide

JetBrains recently published a blog post stating that the IntelliJ platform will completely stop using Log4j and will switch to java.util.logging as the standard logging framework, a change slated for the 2022.1 release.

The decision aims to eliminate false security alerts and reduce the attack surface, especially after the Log4j2 vulnerabilities disclosed last year. Although the platform’s logging requirements are minimal, it still needs file and console output with configurable log levels, which the standard JDK logging API satisfies.

JetBrains will provide stub implementations of the Log4j API that redirect output to java.util.logging (derived from the SLF4J project). Because the stubs are not fully functional, developers may need to adjust their code to maintain full plugin functionality.

Migration recommendations include:

If your plugin code uses Log4j, switch to the standard platform logging API com.intellij.openapi.diagnostic.Logger .

If your own code (outside the plugin) uses Log4j, migrate to the SLF4J API, which the IntelliJ platform implements via java.util.logging .

If a dependency uses Log4j, ask its maintainer to switch to SLF4J; otherwise, use the Log4j‑SLF4J bridge.

If you customize Log4j API usage for SLF4J, replace it with java.util.logging configuration handlers and log levels.

When configuring Log4j via XML for tests, switch to property‑file configuration as described in the LogManager documentation, using the system property idea.log.config.properties.file to specify the path.

These changes will appear in the upcoming 221.4165.x EAP version, allowing developers to test compatibility. JetBrains also clarified that the IDEs use a patched Log4j 1.2 version, so they are not affected by the recent Log4j2 exploits.

Overall, the migration eliminates security concerns and aligns the IntelliJ platform with the standard JDK logging facilities.