[LOG4J2-3232] Log4j 3.0 - Better Java SE modules dependency

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.16.0
• Component/s: Core
• Epic Link: Log4j-core modularization
• Assignee: Unassigned
• Reporter: Bruno Borges
• Created: 15/Dec/21 01:20
• Updated: 17/Jan/22 21:52
• Resolved: 17/Jan/22 21:52

Description

Due to its legacy pre-Java 9 JPMS era, Log4j 2 Core currently has strong dependencies to 'java.desktop' and 'java.management' modules. Log4j 2 Core breaks and does not work properly without these two modules.

Module 'java.naming' is referenced but optional for proper runtime operation. The RCE vulnerability reported in December 2021 towards Log4j 2.x can be mitigated in any Java 9+ version as long the runtime had been assembled with jlink and excluding 'java.naming' module.

As Log4j is reimagined for a 3.0 major new release, it would be recommended to have a Core module that relies solely on 'java.base' and 'java.logging', while separating/publishing different functionalities as separate artifacts/modules, so users can consume them on-demand.