Please disregard, I see this was already done in https://github.com/apache/logging-log4j2/commit/b3c13758ccd68ace56bf1a398f05af9862dbcc2c .
Den tirs. 30. apr. 2024 kl. 17.45 skrev Stig Rohde Døssing < stigdoess...@gmail.com>: > Hi. > > LoggerContext contains references to java.beans due to the use of a few > listener-related classes, which are exposed in the API of LoggerContext. > > > https://github.com/apache/logging-log4j2/blob/6219e667fdc5aa19e23b699b5eb82dd6d9c61691/log4j-core/src/main/java/org/apache/logging/log4j/core/LoggerContext.java#L23 > > Would it be possible to replace these classes with log4j specific variants > some future version, or is breaking the API of LoggerContext a non-starter? > > I'm asking because java.beans is part of the java.desktop module of the > JDK, which means the use of these two classes in LoggerContext prevents > stripping out 35MB of UI-related classes from the JDK when creating a > custom runtime image via jlink, which seems unfortunate. >
