[ 
https://issues.apache.org/jira/browse/JCR-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553531#comment-17553531
 ] 

Julian Reschke commented on JCR-4796:
-------------------------------------

Thanks, Konrad.

Trying to explain again...: Jackrabbit modules use the SLF4J API. This is a 
*compile* time dependency. At *runtime*, they need an implementation of that 
API. This gives you the ability to use whatever logger you want (as long there 
is a SLF4H binding for it).

Jackrabbit modules in general do not include a binding at all, except when it's 
needed for the purposes of the module (such as  standalone JAR, or a demo 
webapp project). It's probably best to assemble the modules that you really 
need in a separate project instead of relying on what we have put into a demo 
project in the past. 

> 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)

Reply via email to