[
https://issues.apache.org/jira/browse/LOG4J2-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648211#comment-13648211
]
Ralph Goers commented on LOG4J2-235:
------------------------------------
Maven has different dependency scopes. See
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
Compile scope means the dependency is required to compile, and therefore also
to run. If you mark it as optional then it won't be pulled in as a transitive
dependency. Requiring jconsole.jar for core would be similar to requiring an
eclipse jar or similar. An application running as a server would never want
that jar included and it really doesn't make much sense to have the JConsole UI
classes in core.
> 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]
