[
https://issues.apache.org/jira/browse/JCR-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551542#comment-17551542
]
Konrad Windszus commented on JCR-4796:
--------------------------------------
SLF4J API is used in JR all over the place (that was a deliberate decision). It
can't be removed. Probably you have more than one SLF4J API in your classpath.
Without further details (which JR version, which JR JARs in classpath, which
servlet container) it is impossible to tell tough what is wrong here.
> 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)
