logging-log4j-dev mailing list archives

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

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

Ralph Goers commented on LOG4J2-235:
------------------------------------

jconsole.jar should definitely not be a required dependency. Optional, maybe. I tend to think
that moving the Jconsole support to a separate jar project makes sense since it only has value
within jconsole.
                
> 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