[
https://issues.apache.org/jira/browse/LOG4J2-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649266#comment-13649266
]
Remko Popma commented on LOG4J2-237:
------------------------------------
Gary, I would not be in favor of moving this to Chainsaw.
The purpose of the JMX gui classes was to be a super-lightweight way for users
to diagnose log4j configuration issues and fix such issues on a live system
*without requiring a restart*. AFAIK no other logging package offers this and I
would consider this core log4j functionality.
However you have a good point about adding yet another jar.
Now that we are assembling core and jmx-gui, why don't we take this opportunity
to revisit the one jar idea (LOG4J2-109) and expand this assembly to add all
components?
There seem to be 2 schools of thought, one (Maven users?) who prefer separate
jars for fine-grained control over dependencies, and another one of users who
don't want that flexibility. I can see both points of view. Why not make both
groups of users happy?
We already have all the separate jars, so why not also have one jar that
combines all components?
(The only component that cannot be included for technical reasons is
log4j-to-slf4j, and seeing what that component does it would not make sense to
include it anyway.)
We could call this jar simply:
log4j-2.0.jar
> 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]
