On 9/17/2023 8:09 AM, Shawn Heisey via slf4j-user wrote:
> On 9/16/2023 3:36 PM, Ceki Gülcü via slf4j-user wrote:
>>> I have learned that although Solr does include the jul-to-slf4j
>>> jar, this bridge does not get activated just by having the jar in
>>> the classpath. It must be activated eith
On 9/16/2023 3:36 PM, Ceki Gülcü via slf4j-user wrote:
I have learned that although Solr does include the jul-to-slf4j
jar, this bridge does not get activated just by having the jar in
the classpath. It must be activated either in the code or in the
JUL config.
That is correct.
How do I do t
Hi Shawn,
Comments below.
On 9/16/2023 10:45 PM, Shawn Heisey via slf4j-user wrote:
[cut]
> I have learned that although Solr does include the jul-to-slf4j
> jar, this bridge does not get activated just by having the jar in
> the classpath. It must be activated either in the code or in the
>
I am a committer on the Apache Solr project.
The primary dependency that Solr has is Lucene, and there are a LOT more
dependencies.
The lucene-core jar has zero dependencies, and their intent is to keep
it that way. So when they needed to implement logging, they did so
using java.util.loggi
