logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-235) Dependency on tools.jar and jconsole
Date Fri, 03 May 2013 14:22:17 GMT

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

Remko Popma commented on LOG4J2-235:
------------------------------------

Nick, I'm not disagreeing with you. 
I removed tools.jar as soon as it was pointed out. 
I made jconsole.jar optional as soon as I understood how this transitive dependency thing
works in maven. 

There is no (and never was any) dependency on JDK classes for anyone using log4j. 
The class in question is only used when you run
  $JAVA_HOME/bin/jconsole -pluginpath log4j-core-<version>.jar
(and you would need a JDK to run that command anyway)

Removing tools.jar and making jconsole.jar optional was high-priority as it was affecting
users. 

Moving the JMX GUI classes into a separate submodule (I'd like to call it log4j-jmx-gui) is
on the todo list, but not at the top anymore. There are a handful of bugs and there's your
DB appenders patch that I all consider higher priority and I plan to look at those first before
the module reshuffling. 

Let me know if you think I am prioritizing things wrong. 

                
> 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


Mime
View raw message