cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Federico Fernández (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-13961) Safe castings to logback classes
Date Tue, 17 Oct 2017 12:37:00 GMT

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

Federico Fernández resolved CASSANDRA-13961.
--------------------------------------------
       Resolution: Duplicate
    Reproduced In: 3.11.0, 3.10  (was: 3.10, 3.11.0)

> 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
>              Labels: patch
>         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


Mime
View raw message