[
https://issues.apache.org/jira/browse/LOG4J2-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604379#comment-15604379
]
Romain Manni-Bucau commented on LOG4J2-1650:
--------------------------------------------
Ok, so the use cases could be sumarrized as "runtime dependency usage".
Concretely used by any other part of a software that the business code (=
library or server) the size is a criteria to take into account cause something
making possible a user to reject the library. Of course the library can "only"
use -api but you always need -core so it is a mandatory dependency whatever
you do. The other use case is a small project we are building @openwebbeans
which will provide a runnable fatjar. In this last case we shade all the
dependencies and it would be great to be able to use log4j2 but the central
features we want to deliver are console logging, rolling files and maybe
highlighting. Everything else just makes the jar bigger for no gain. The idea
would be to let the user add its own libraries and complementary log4j2 modules
if needed. This small project has a limit of ~10M for its fatjar and log4j2 is
already 1.3M which is quite impacting for us even if not blocking (yet?).
> log4j2-core diet
> ----------------
>
> Key: LOG4J2-1650
> URL: https://issues.apache.org/jira/browse/LOG4J2-1650
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
>
> Hello,
> log4j2 is ~1.3M. It is a lot to get started with logging and several parts
> are not mandatory to start and rarely needed all together like jackson, db,
> yaml (this one is not that big) etc...Also saw Generate class which is quite
> big but not sure it is needed at runtime and the annotation processor logic
> is never needed at runtime.
> Anyway, by comparison logback and log4j1 are ~500k so hopefully we could only
> pay the same price to get started with log4j2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
