[
https://issues.apache.org/jira/browse/LOG4J2-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649288#comment-13649288
]
Remko Popma commented on LOG4J2-237:
------------------------------------
1. Agreed, it is the "all-possible-in-one" jar. log4j-to-slf4j is a bit of a
black sheep as it leads users away (astray?) from the True Way (core) of Log4j
2.0. Tongue-in-cheek, but I think we all agree that this one is not invited to
the one-jar party.
2. I don't propose to make any change to existing dependencies.
Maven users can keep using the individual components and should not be affected.
Perhaps we should not even publish the combined jar to Maven Central.
3. The use case you describe is users having a single application that uses
multiple logging packages simultaneously, and that is configured separately for
each logging package. A single log4j-2.0.jar would give these users the option
to combine the separate configurations into a single unified configuration.
This is a huge plus and we should put this on the web site as Yet Another
Reason To Switch to log4j 2.0. (Not joking.)
Naturally, users who want to keep individual configurations for each logging
package can use the log4j-api and log4j-core individual module jars and they
won't be affected.
4. I would lean towards including everything possible. Why not? Everything else
is just a matter of taste.
> 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]
