[
https://issues.apache.org/jira/browse/LOG4J2-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648056#comment-13648056
]
Nick Williams commented on LOG4J2-235:
--------------------------------------
Compile time dependencies would, by nature, also be runtime dependencies.
If this compiles without tools.jar, then tools.jar definitely needs to be
removed as a dependency.
As far as the JMX classes, my (limited) understanding of JMX is that there
would be two parts: the "server-side" code (that is, the code running within
the application that is using Log4j, and that is running a JMX server) and the
"client-side" code (the JConsole plugin). I think packaging these in the same
artifact/JAR might not be correct.
I definitely think that the "server-side" code should be in the log4j-core
artifact. This makes sense. However, the JConsole (GUI) code would never be
used within the logging application (as far as I can tell). I think this could
serve as an argument for moving the JConsole plugin code into a
log4j-jconsole-plugin artifact. If the JConsole plugin/GUI code is the only
code that depends on jconsole.jar, I think that makes a STRONG argument for
moving the JConsole plugin code into a log4j-jconsole-plugin artifact.
> Dependency on tools.jar and jconsole
> ------------------------------------
>
> Key: LOG4J2-235
> URL: https://issues.apache.org/jira/browse/LOG4J2-235
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0-beta5
> Environment: Windows 7, 64 bit, Maven 3.0.5, Java 1.6
> Reporter: Sebastian Oerding
>
> Hello,
> when switching from 2.0-beta4 to 2.0-beta5 I something irritating that in the
> dependency hierarchy of my project. For log4j2-core there were transitive
> dependencies on tools.jar and jsconsole which had not been there.
> This looks like a bug and an as a consequence requires a JDK instead of a
> JRE (at least due to the tools.jar which does not exist in Java 1.6 JRE). If
> these dependencies are really required, it should be clearly stated.
--
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]
