[
https://issues.apache.org/jira/browse/LOG4J2-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696435#comment-17696435
]
Jannik Zuther edited comment on LOG4J2-2870 at 3/4/23 2:30 PM:
---------------------------------------------------------------
Still seems to be the case in `3.0.0` (Snapshot versions) as of right now. I
hope it's still planned to get rid of this dependency. The `java.desktop`
module is also comparatively huge, and bloats the size of any runtime image
that is created with `jlink`.
was (Author: blacklands):
Still seems to be the case in `3.0.0` as of right now. I hope it's still
planned to get rid of this dependency. The `java.desktop` module is also
comparatively huge, and bloats the size of any runtime image that is created
with `jlink`.
> 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
> Fix For: 3.0.0
>
>
> 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.20.10#820010)
