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 Fri, 03 May 2013 02:34:15 GMT

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

Nick Williams commented on LOG4J2-235:

Glad to hear tools.jar wasn't actually needed.

Part of the issue is classpath pollution. By putting jconsole.jar on the classpath in the
core JAR, other Log4j developers could accidentally use classes from jconsole.jar within other
features in the core module. This could have negative consequences for the end-user (granted,
that would be detected and corrected pretty quickly).

The other problem, however, is JAR pollution. The JConsole GUI plugin classes in log4j-core
will never be used in applications that normally use log4j-core. For that matter, log4j-core
and all other artifacts in Log4j right now are intended to be Maven central artifacts or otherwise
libraries that are packaged with the resulting application. But the JConsole GUI plugin classes
are NOT intended for that. They will be have to be manually downloaded and placed somewhere
(usually on an application administrator's computer) from where they can be put on the classpath
when running JConsole. This is a very different context and a very different need. The log4j-jconsole-plugin
wouldn't even need to be published in Maven central (though there would be no harm in doing
so). I don't think this creates the "Yet Another Jar" problem that it sounds like. It's not
"Yet Another Jar" that would ever go in an application.

Just my $0.02.
> 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