[
https://issues.apache.org/jira/browse/JCR-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552688#comment-17552688
]
Julian Reschke commented on JCR-4796:
-------------------------------------
As Konrad said, using slf4j is a deliberate decision, and is done in many other
projects as well. It's unfortunate that you have a problem with a class
conflict, and it would be good to understand what exactly goes wrong here.
I find out a bit funny that, in another ticket, you just asked for adding an
(optional) runtime dependendy to make things easier for you to configure, and
here you ask to remove a required dependency.
> 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)
