[
https://issues.apache.org/jira/browse/LOG4J2-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541863#comment-15541863
]
Mikael Ståldal commented on LOG4J2-1627:
----------------------------------------
If we should reorganize the project, there is another issue we should consider:
transitive dependencies
Currently, log4j-core has quite some optional dependencies. I don't like that
since the user needs to manually keep track of which transitive runtime
dependencies to use, efficiently negating the advantage of using Maven (or Ivy,
Gradle, SBT) in the first place.
If we should split up log4j-core, then I would like to move out everything that
have transitive dependencies to their own modules, and make those dependencies
non-optional in those new modules.
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
