You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2018/09/08 16:25:00 UTC

[jira] [Commented] (LOG4J2-2438) Using log4j-core as a module and usage in JLink

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

Ralph Goers commented on LOG4J2-2438:
-------------------------------------

Last I checked, not all of Log4j's optional dependencies have been modularized. I am not sure we can create a module using names we can't rely on. In the 3.0 branch we are trying to split out many of the optional dependencies but we won't be able to remove them all.  For example, I can't find any module information for Jackson. 

Any help you can provide to resolve this would be welcome.

> Using log4j-core as a module and usage in JLink
> -----------------------------------------------
>
>                 Key: LOG4J2-2438
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2438
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.11.1
>            Reporter: Karl Heinz Marbaise
>            Priority: Critical
>
> Currently based on the given automatic modules you can't use log4j-core in a project where you like to use jlink to produce a runtime image..
> Related to LOG4J2-2226



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)