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

Posted to commits@cassandra.apache.org by "Federico Fernández (JIRA)" <ji...@apache.org> on 2017/10/17 09:31:00 UTC

[jira] [Created] (CASSANDRA-13961) Safe castings to logback classes

Federico Fernández created CASSANDRA-13961:
----------------------------------------------

             Summary: Safe castings to logback classes
                 Key: CASSANDRA-13961
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13961
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Federico Fernández
            Priority: Minor
             Fix For: 3.11.1, 3.11.0, 3.10
         Attachments: LogbackPatch.patch

While working in an SBT plugin for I faced the problem: the system was injecting in the classpath the log4j implementation for SLF4J. This caused a {{ClassCastException}} in the startup process.

Cassandra uses logback but IMHO we shouldn't fail at runtime if SLF4J loads another implementation. Ideally, we should allow the users to choose their favourite implementation.

I've attached a patch that adds a {{instanceof}} checkings before casting the logback classes.

Thanks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org