[
https://issues.apache.org/jira/browse/LOG4J2-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936790#comment-16936790
]
Gary Gregory commented on LOG4J2-2699:
--------------------------------------
You can take a look at the `master` branch where we've started to move code out
of the core jar into new modules. No quick solution here unfortunately.
> Please reduce the size of log4j-core.jar
> ----------------------------------------
>
> Key: LOG4J2-2699
> URL: https://issues.apache.org/jira/browse/LOG4J2-2699
> Project: Log4j 2
> Issue Type: Task
> Components: Core
> Reporter: Adrian Cole
> Priority: Major
>
> The log4j-core jar is quite large now, 2MiB, and including a lot of
> functionality irrelevant to others. For example, a quarter meg is "picocli"
> and also the maven pom internally is huge. It seems there could be some quick
> wins to reduce it. Alternatively, create a jar that is dedicated to commodity
> feature vs the kitchen sink. Zipkin is trying to make a slim build and log4j2
> is one of our largest dependencies
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
