You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2013/11/30 09:34:36 UTC

[jira] [Commented] (KARAF-2593) pax-logging-api, slf4j and logback package export conflict

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

Jean-Baptiste Onofré commented on KARAF-2593:
---------------------------------------------

1/ slf4j is not OSGi compliant by default
2/ pax-logging-api is just the API, and the latest slf4j-api "compliant" is 1.7.1, slf4j 1.7.5 contains fixes on the service, not the API

> pax-logging-api, slf4j and logback package export conflict
> ----------------------------------------------------------
>
>                 Key: KARAF-2593
>                 URL: https://issues.apache.org/jira/browse/KARAF-2593
>             Project: Karaf
>          Issue Type: Dependency upgrade
>    Affects Versions: 3.0.0
>            Reporter: ChengRen
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 3.0.0
>
>
> The newest version of pax-logging-api is1.7.1 which export slf4j 1.7.1 . But slf4j-api's newest version is 1.7.5 and also import slf4j.impl with version 1.6.0. And logback's newest version is 1.0.13 which export slf4j.impl(1.7.5). 
> Karaf use pax-logging-api as slf4j bundle, which is becoming lagged behand slf4j.  should we switch back to slf4j or upgrade pax-logging-api to newer version?



--
This message was sent by Atlassian JIRA
(v6.1#6144)