+1 Allow me to remind everyone that anything that is removed from `3.0.0` can be added again in a follow up minor release, if need arises. Hence, no need to be overcautious.
On Mon, Jan 15, 2024 at 9:50 PM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi all, > > While 3.x is approaching its first stable release as a meteor burning > through the sky, its core is getting smaller as it approaches earth. > > That is why I would propose to remove two further modules from 3.x: > > * The functionality of `log4j-jcl` is included in `commons-logging` > version 1.3.0 (and previously it was also provided by `spring-jcl`). I > assume that users migrating to Log4j 3.x can also migrate to > `commons-logging` 1.3.0. > > * The Jetty 9.x logger, which is half of the functionality of > `log4j-appserver`, can be replaced by `log4j-slf4j-impl` if the users > are willing to migrate to Jetty 10.x. Since community support for > Jetty 9.x ended two years ago, I guess user will migrate to a > supported Jetty version first and only then think about Log4j 3.x. > > * The Tomcat logger (the other half of `log4j-appserver`) is only > part of the puzzle of artifacts required to have a fully functional > logging system in Tomcat. I usually also needed my own artifacts from > copernik-eu/log4j-plugins[1] to have something comparable (but still > worse) than what WildFly has. I can adopt this part of > `log4j-appserver` into copernik-eu/log4j-plugins and make a release > before Log4j 3.0.0 is out. If there is any user interest in it, I can > "contribute back" the Tomcat logger and other components in a future > release. > > What do you think? > > [1] https://github.com/copernik-eu/log4j-plugins >
