You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Can Gencer (Jira)" <ji...@apache.org> on 2020/06/15 11:44:00 UTC
[jira] [Updated] (LOG4J2-2870) Dependency on PropertyChangeListener
and PropertyChangeEvent
[ https://issues.apache.org/jira/browse/LOG4J2-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Can Gencer updated LOG4J2-2870:
-------------------------------
Description: There is currently a dependency on PropertyChangeListener and PropertyChangeEvent in LoggerContext. These classes are coming from java.beans package which is inside the java.desktop module. This prevents packaging a server-side only JVM with minimal dependencies when using log4j2 because you have to bundle in the whole of the desktop module. (was: There is currently a dependency on `PropertyChangeListener` and `PropertyChangeEvent` in `LoggerContext`. These classes are coming from `java.beans` package which is inside the `java.desktop` module. This prevents packaging a server-side only JVM with minimal dependencies when using log4j2 because you have to bundle in the whole of the desktop module.)
> Dependency on PropertyChangeListener and PropertyChangeEvent
> -------------------------------------------------------------
>
> Key: LOG4J2-2870
> URL: https://issues.apache.org/jira/browse/LOG4J2-2870
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.12.1
> Reporter: Can Gencer
> Priority: Major
>
> There is currently a dependency on PropertyChangeListener and PropertyChangeEvent in LoggerContext. These classes are coming from java.beans package which is inside the java.desktop module. This prevents packaging a server-side only JVM with minimal dependencies when using log4j2 because you have to bundle in the whole of the desktop module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)