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

Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2017/04/08 03:27:42 UTC

[jira] [Resolved] (CASSANDRA-13424) Explicit usage of logback

     [ https://issues.apache.org/jira/browse/CASSANDRA-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Jirsa resolved CASSANDRA-13424.
------------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 3.10)

> Explicit usage of logback
> -------------------------
>
>                 Key: CASSANDRA-13424
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13424
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Platon Bibik
>            Priority: Blocker
>
> I am trying to use Cassandra as an embedded service in my app's test suite. My code writes logs through an slf4j interface with log4j2 as a backend, while Cassandra contains a logback-classic dependency, which provides binding that conflicts with my log4j2 binding. I can't just exclude this dependency since there are explicit usages of logback's classes in org.apache.cassandra.cql3.functions.ThreadAwareSecurityManager, that were added in commit 3ae01ddc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)