+1 Piotr, you populated #2163 <https://github.com/apache/logging-log4j2/issues/2163> tasks last week and there asked to port `log4j-jcl` changes from `2.x` to `main`. That is what I spent my yesterday with. I would appreciate it if you can share these kinds of developments earlier. Putting that aside, thanks for following up on `log4j-jcl` and I think it is good that we can drop it.
On Wed, Jan 10, 2024 at 11:11 PM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi all, > > Since `commons-logging` 1.3.0 was published last month and it supports > Log4j API out-of-the-box, does it still make sense to keep `log4j-jcl` > around in 3.x? > > I would keep the 2.x version, so that users don't need to modify their > stacks. However we might assume that 3.x adopters are already running > the latest versions of the remaining dependencies, specifically they > upgraded `commons-logging`. This is why I would propose to remove > `log4j-jcl` from 3.x. > > Remark that Spring users have been using `spring-jcl` for a very long > time (which also supports the Log4j API), so they didn't need > `log4j-jcl` either. > > Piotr >
