[
https://issues.apache.org/jira/browse/LOG4J2-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649269#comment-13649269
]
Ralph Goers commented on LOG4J2-237:
------------------------------------
This discusion really should happen in LOG4J2-109 but...
1. You cannot have an "all-in-one" jar that contains everything. As you point
out, it will result in the problem that you fixed where slf4j-impl and
log4j-to-slfj4 cannot be bundled together.
2. It will result in a whole lot of dependencies being made optional, which is
actually much harder for Maven users (probably Ivy and Groovy too, I would
imagine).
3. It forces users to map JCL, Log4j 1.x and SLF4J to Log4j 2. If they think
they are just upgrading from Log4j 1.x to Log4j 2.x but have other logging
components they will have conflicts.
4. I'm not sure that the tag library makes sense in an "all-in-one" jar.
So the problem isn't just about Maven.
> Move JMX GUI classes out of the core module into a new submodule
> ----------------------------------------------------------------
>
> Key: LOG4J2-237
> URL: https://issues.apache.org/jira/browse/LOG4J2-237
> Project: Log4j 2
> Issue Type: Dependency upgrade
> Components: Core
> Affects Versions: 2.0-beta5
> Reporter: Remko Popma
> Assignee: Remko Popma
> Priority: Minor
> Fix For: 2.0-beta6
>
>
> See discussion in LOG4J2-235.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
