[jira] [Updated] (LOG4J2-2226) Make log4j-core a Java 9 module

["Remko Popma (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remko Popma updated LOG4J2-2226:
--------------------------------
    Description: 
Log4j-core is currently an automatic module.

By making it a real module the Java platform can help enforce the distinction between internal and exported classes.

This epic links together tickets related to this goal. I expect that most of the work will be about:
 * moving external dependencies out of the core module 
 * reorganizing packages and classes into internal and exported packages. Other Log4j modules and custom plugins can depend on the exported packages but not the internal ones. 

  was:
Log4j-core is currently an automatic module. 

By making it a real module the Java platform can help enforce the distinction between internal and exported classes. 

This epic links together tickets related to this goal. 


> Make log4j-core a Java 9 module 
> --------------------------------
>
>                 Key: LOG4J2-2226
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2226
>             Project: Log4j 2
>          Issue Type: Epic
>          Components: Core
>            Reporter: Remko Popma
>            Priority: Major
>
> Log4j-core is currently an automatic module.
> By making it a real module the Java platform can help enforce the distinction between internal and exported classes.
> This epic links together tickets related to this goal. I expect that most of the work will be about:
>  * moving external dependencies out of the core module 
>  * reorganizing packages and classes into internal and exported packages. Other Log4j modules and custom plugins can depend on the exported packages but not the internal ones. 



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