[
https://issues.apache.org/jira/browse/LOG4J2-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648398#comment-13648398
]
Nick Williams commented on LOG4J2-235:
--------------------------------------
Alright, let me clear a few things up, because it sounds like there may be some
confusion, and that's the last thing I want. :-)
First of all, tools.jar probably isn't ever required. It contains utilities for
running the compiler, JavaDoc, and other normally-executable utilities from the
Java API instead of the command line. It doesn't contain any JMX or JConsole
classes that I can see. So I think removing it as a dependency is safe.
Now as far as I can tell jconsole.jar is required for compiling and running the
GUI JMX classes. Even if it WERE required for the other JMX classes, it would
never be required to COMPILE an application that was using Log4j. It would only
be required to RUN an application using Log4j (which means the running
application would have to be running in a JDK).
Of course, we certainly don't want to introduce a dependency on a JDK in order
to use Log4j. As I said, my suspicion is that these JDK-only classes are ONLY
required for the GUI classes. However, the best way to ensure this is, as many
have agreed here, to move the GUI classes into a separate submodule
(log4j-jconsole-plugin, or similar). Then, we should be able to remove the
jconsole.jar dependency from the Core since it would only be required in the
submodule.
Hope this clears a few things up.
> 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]
