[
https://issues.apache.org/jira/browse/CASSANDRA-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961661#comment-15961661
]
Jeff Jirsa commented on CASSANDRA-13424:
----------------------------------------
This is a duplicate of CASSANDRA-13396 , which is sorta patch available, but
the patch needs a few modifications before it'll be committed.
Note, though, that log4j2 isn't officially tested, and therefore isn't
expressly supported.
> 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)
