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
