You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2020/03/06 15:43:00 UTC
[jira] [Commented] (LOG4J2-2802) Log4j-core must only require
java.base
[ https://issues.apache.org/jira/browse/LOG4J2-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053537#comment-17053537 ]
Gary D. Gregory commented on LOG4J2-2802:
-----------------------------------------
How can we test this when done? I imagine we'd want the same test for log4j-api.
> Log4j-core must only require java.base
> --------------------------------------
>
> Key: LOG4J2-2802
> URL: https://issues.apache.org/jira/browse/LOG4J2-2802
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.0.0
> Reporter: Ralph Goers
> Priority: Major
>
> One of the main goals of 3.0.x is to have each of the log4j jars be declared with a module-info.java file to make it be a true participant in JPMS. When creating the module-info.java for Log4j core it needs to only have a required dependency on the java.base module. This means things like:
> * The script engine is included in java.scripting
> * XML processing is generally in java.xml.
> must either be able to be declared as transitive dependencies or be separated into their own modules.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)