On Thu, Jan 25, 2018 at 9:05 AM, Mikael Ståldal <mi...@apache.org> wrote:
> Yes, but it is unfortunate that the worry about the main repo size make us > hesitate splitting out stuff from log4j-core into own modules. And, with perfect timing: https://issues.apache.org/jira/browse/LOG4J2-1863?focusedCommentId=16339319&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16339319 Gary > > > > On 2018-01-24 22:37, Ralph Goers wrote: > >> They are not really orthogonal. >> >> 1. Log4j core contains some stuff that isn’t really “core” >> functionality., such as Kafka or JMS. These cause the core tests to take >> longer than necessary. >> 2. The size of the repo directly effects how long a build takes to run, >> as does the number of components in core. >> >> >> >> On Jan 24, 2018, at 2:24 PM, Mikael Ståldal <mi...@apache.org> wrote: >>> >>> Yes, and it's unfortunate that they get conflated. >>> >>> On 2018-01-21 16:55, Gary Gregory wrote: >>> >>>> I can see two main orthogonal issues: >>>> - The size of the git repo. >>>> - The size of the log4j-core module. >>>> >>> >>> >> >> >
