Hello Volcan, On Fri, 29 Apr 2022 at 22:04, Volkan Yazıcı <[email protected]> wrote:
> I have raised this issue in the past. I even came up with a proposal on the > repository structure > <https://lists.apache.org/thread/sdv92pw6m9bst8zzn88jyln8z8ozshw3> to be > followed. I am a big proponent of breaking up the logging-log4j2 repository > into multiple ones. The current size of the code base is simply > incomprehensible and slows down the development cycle tremendously due to > excessive compilation and test times. > I agree with the proposal, although the exact split would require a longer discussion. For my part: *logging-log4j2-api* > log4j-1.2-api > log4j-api > log4j-1.2-api should be probably in another repository, maybe with the other bridges, *logging-log4j2-jee* > log4j-appserver > log4j-taglib > log4j-web > If we split these up, does it mean we can add additional features to these modules? E.g. a JNDI and Servlet property source or some additional lookups? Your remark against merging https://github.com/apache/logging-log4j2/pull/731 was that additional features will make the repository harder to maintain. log4j-osgi > Clearly this one should be with `log4j-core`, since it consists of `log4j-core` tests in an OSGI environment. Piotr
