ppkarwasz commented on issue #1865:
URL:
https://github.com/apache/logging-log4j2/issues/1865#issuecomment-1768409301
There are some workarounds:
1. JCL has many ways to configure a `LogFactory` (that is probably why our
tests didn't detect it). For example you can add a `commons-logging.properties`
file with content:
```
org.apache.commons.logging.LogFactory =
org.apache.logging.log4j.jcl.LogFactoryImpl
```
(I submitted this as HtmlUnit/htmlunit#651)
1. You can replace `commons-logging:commons-logging` with
[`org.springframework:spring-jcl`](https://mvnrepository.com/artifact/org.springframework/spring-jcl),
which is a **drop-in** replacement for JCL, that logs directly to the Log4j
API (hence no need for `log4j-jcl` any more).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
