Hi, On Tue, 9 Apr 2024 at 21:34, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > * `log4j-iostreams`, > * `log4j-jpl`, > * `log4j-jul`, > * `log4j-slf4j-impl`, > * `log4j-slf4j2-impl`, > * `log4j-to-jul`, > * `log4j-to-slf4j`.
Don't get me wrong: these are very good artifacts, but I really don't know how to make the "3.x ready". If breaking changes are required to these modules, we can do them any time. The same applies to `log4j-docker`: I really don't know how a `3.x` version will be better than a `2.x`. Sure, we replace `Log4j2Plugins.dat` with a Java service so it is easier to build JPMS applications that use `log4j-docker` (the JVM loads all the modules that provide a service automatically). However users can still use the `2.x` version of `log4j-docker` by adding an explicit `requires` directive or `--add-modules` on the command line. We are not planning to introduce **any** changes to `StrLookup` any time soon, so 2.x modules like `log4j-docker` or the newly released by Fabric8 `kubernetes-log4j`, will be compatible with Log4j Core 3.x. Piotr
