[
https://issues.apache.org/jira/browse/LOG4J2-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-1627.
---------------------------------
Resolution: Won't Fix
> Move components from the Log4j 2 build into a separate build.
> -------------------------------------------------------------
>
> Key: LOG4J2-1627
> URL: https://issues.apache.org/jira/browse/LOG4J2-1627
> Project: Log4j 2
> Issue Type: Improvement
> Affects Versions: 2.8
> Reporter: Ralph Goers
> Priority: Major
>
> The Log4j build has grown to the point that performing releases is very time
> consuming. One way to help with this is to move some components, especially
> those that are not typically modified frequently, to another project. Almost
> everything besides the API, Core, web and the various bridges could be moved.
> In addition, some core components could be considered for moving to another
> module such as the mom and db appenders. Perhaps even the JMX support could
> be moved.
> We should also take into consideration making things line up with the Java
> profile system in Java 8 and the Java 9 module system.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
