ppkarwasz commented on PR #2895: URL: https://github.com/apache/solr/pull/2895#issuecomment-2530882606
> * [jul-to-slf4j](https://github.com/qos-ch/slf4j/blob/v_2.0.16/jul-to-slf4j/LICENSE.txt) Since you use Log4j Core in your binary distribution, you should consider using the [JUL-to-Log4j API bridge](https://logging.apache.org/log4j/2.x/log4j-jul.html) instead. The artifact has two _modi operandi_: * A fast bridge, which replace JUL entirely, but requires the setting of the `java.util.logging.manager` Java system property in your startup scripts (see [Using LogManager](https://logging.apache.org/log4j/2.x/log4j-jul.html#bridge-logmanager)). * A slower bridge, similar to the one in `jul-to-slf4j`, but it provides direct bridging between JUL and Log4j API (without passing through SLF4J). See [Using Log4jBridgeHandler](https://logging.apache.org/log4j/2.x/log4j-jul.html#bridge-handler). > * jcl-over-slf4j, this changed from MIT to ASL in [repo](https://github.com/qos-ch/slf4j/blob/v_2.0.16/jcl-over-slf4j/LICENSE.txt), but is still using the [base license](https://github.com/qos-ch/slf4j/blob/v_2.0.16/LICENSE.txt) in downloaded package. Not sure which one to use in this case. @janhoy any idea how to handle these cases? Prefer ASL? Since the release of `commons-logging` 1.3.0, `jcl-over-slf4j` (as well as `spring-jcl` and `log4j-jcl`) are no longer necessary. We made [a blog post about it](https://logging.apache.org/blog/2023/12/02/apache-common-logging-1.3.0.html) last year. -- 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: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
