[
https://issues.apache.org/jira/browse/JCR-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553730#comment-17553730
]
Julian Reschke edited comment on JCR-4796 at 6/13/22 5:34 PM:
--------------------------------------------------------------
bq. In my case I'm only deploying jackrabbit-jcr2dav and jackrabbit-spi2dav -
no wars, nothing extra yet, and none of this works out the box. I want to fix
this by reverting to JUL at the lowest levels.
The right fix is to identify the problem and fix it. It's supposed to work. Of
cource you *could* fork Jackrabbit and ove to a different logging API, but of
course forking comes with disadvantages.
bq. Moving on to the test suite, when the jackrabbit test suite is run from
within Eclipse, we get this logged complaining about multiple slf4j bindings,
and nothing logged from the test itself:
Which subproject? And is this reproducable directly from Maven?
was (Author: reschke):
> In my case I'm only deploying jackrabbit-jcr2dav and jackrabbit-spi2dav - no
> wars, nothing extra yet, and none of this works out the box. I want to fix
> this by reverting to JUL at the lowest levels.
The right fix is to identify the problem and fix it. It's supposed to work. Of
cource you *could* fork Jackrabbit and ove to a different logging API, but of
course forking comes with disadvantages.
>Moving on to the test suite, when the jackrabbit test suite is run from within
>Eclipse, we get this logged complaining about multiple slf4j bindings, and
>nothing logged from the test itself:
Which subproject? And is this reproducable directly from Maven?
> Remove slf4j from Jackrabbit libraries
> --------------------------------------
>
> Key: JCR-4796
> URL: https://issues.apache.org/jira/browse/JCR-4796
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Reporter: Graham Leggett
> Priority: Major
>
> Life is too short to deal with exceptions like this one:
> java.lang.LinkageError: loader constraint violation: when resolving method
> 'org.slf4j.ILoggerFactory
> org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()' the class loader
> org.apache.catalina.loader.ParallelWebappClassLoader @4bd217c of the current
> class, org/slf4j/LoggerFactory, and the class loader java.net.URLClassLoader
> @7907ec20 for the method's defining class, org/slf4j/impl/StaticLoggerBinder,
> have different Class objects for the type org/slf4j/ILoggerFactory used in
> the signature (org.slf4j.LoggerFactory is in unnamed module of loader
> org.apache.catalina.loader.ParallelWebappClassLoader @4bd217c, parent loader
> java.net.URLClassLoader @7907ec20; org.slf4j.impl.StaticLoggerBinder is in
> unnamed module of loader java.net.URLClassLoader @7907ec20, parent loader
> 'app')
> Remove slf4j and replace with the java default behaviour.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
