You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2016/05/03 08:27:12 UTC

[jira] [Commented] (CAMEL-9936) Camel-parent 17.0 uses incompatible logback-classic and slf4j-api

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

Claus Ibsen commented on CAMEL-9936:
------------------------------------

Camel do not use logback, only slf4j-api as its api for logging.

> Camel-parent 17.0 uses incompatible logback-classic and slf4j-api
> -----------------------------------------------------------------
>
>                 Key: CAMEL-9936
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9936
>             Project: Camel
>          Issue Type: Task
>          Components: camel-core
>    Affects Versions: 2.17.0
>            Reporter: Jay mann
>            Priority: Minor
>
> Camel-parent 17.0 uses logback-classic:1.1.5 and slf4j-api:1.7.13
> These are not compatible and produce the following error: 
> java.lang.NoClassDefFoundError: org/slf4j/event/LoggingEvent
> See the following page:
> http://www.slf4j.org/codes.html
> Logback-classic version 1.1.4 and later require slf4j-api version 1.7.15 or later.
> With an earlier slf4j-api.jar in the classpath, attempting introspection of a Logger instance returned by logback version 1.1.4 or later will result in a NoClassDefFoundError similar to that shown below....



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)