logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-235) Dependency on tools.jar and jconsole
Date Thu, 02 May 2013 15:32:16 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647627#comment-13647627

Nick Williams commented on LOG4J2-235:

I noticed that the other day, too, and almost filed a bug for it. Specifically, this is related
to the JMX implementation in Log4j2 (http://markmail.org/thread/flnzsojwv47ohf4q). However,
as Ralph stated (http://markmail.org/thread/fbs5huavd4zkdz7c), extra dependencies should not
be drug in. This made me think, "well, additional dependencies have been drug in and shouldn't

However, it's important to note that these transitive dependencies system dependencies that
are resolved at runtime and are not, for example, packaged with your WAR file if you're creating
a web application. Other runtime dependencies would normally be shipped in your WAR file.
So the inconvenience here is really only noticed if your IDE is transparent about what it's
downloading. I don't BELIEVE it actually affects anything at runtime.

However, it would be great if Remko could shed some light on this. I'm not exactly clear about
how the JMX support he added to Log4j2 would work unless the application was running in a
JDK instead of a JRE.
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message