[
https://issues.apache.org/jira/browse/LOG4J2-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604425#comment-15604425
]
Mark Struberg commented on LOG4J2-1650:
---------------------------------------
The other issue (beside pure size) is that having woodstox, jackson, etc as
dependencies for a piece which is primarily used as a container lib possibly
creates classpath clashes. We e.g. even got rid of commons-lang3 in bval
recently because we had issues. And the commons people really take a lot of
care to stay bytecode compatible. For quite a few libs you use I would not bet
on such a guaranteed bytecode compatibility!
What happened was the following. Customer uses TomEE which shipped with an
older version of commons-lang3. Some lib (think it was Vaadin) required
lang3-3.4 -> boom. Of course it was easy to fix for me by simply upgrading
TomEE to that lang3 version. But for many developers this is a bit too much.
How many customers do you know which allow to exchange jars in a production
container?
In my opinion container libs like bval, openwebbeans, log4j etc should come
with a minimum of required dependencies. Ideally with none at all. Ofc having
additional 'plugins' is fine, but not in the core jar imo.
> 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]
