[
https://issues.apache.org/jira/browse/LOG4J2-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15719169#comment-15719169
]
Remko Popma commented on LOG4J2-1627:
-------------------------------------
Concrete candidates for being moved to a separate project:
|| (-) Move|| (?) TBD|| (/) Keep||
|log4j-api-scala_2.10|log4j-bom|log4j-1.2-api|
|log4j-api-scala_2.11|log4j-distribution|log4j-api|
|log4j-flume-ng|log4j-osgi|log4j-core|
|log4j-iostreams| | log4j-jcl|
|log4j-jmx-gui| | log4j-jul|
|log4j-liquibase| |log4j-perf|
|log4j-nosql| |log4j-slf4j-impl|
|log4j-samples| |log4j-to-slf4j|
|log4j-taglib| |log4j-web|
> 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
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
