cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CASSANDRA-803) remove PropertyConfigurator from CassandraDaemon
Date Tue, 28 Dec 2010 14:38:45 GMT

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

Jonathan Ellis resolved CASSANDRA-803.
--------------------------------------

    Resolution: Duplicate

bq. As far I can see, the PropertyConfigurator is already removed with rev 934505 for CASSANDRA-971

Right. Closing this one as a duplicate.

bq. setLog4jLevel should be kept, but as some kind of optional operation, just in the case
that log4j is present

This is what we're going with for now.

> remove PropertyConfigurator from CassandraDaemon
> ------------------------------------------------
>
>                 Key: CASSANDRA-803
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-803
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6
>            Reporter: Jesse McConnell
>
> In order for users to make use of the EmbeddedCassandraService for unit testing they
need to have a dependency declared on log4j.  
> It would be nice if we could use the log4j-over-slf4j artifact to bridge this requirement
for those of us using slf4j.  
> http://www.slf4j.org/legacy.html#log4j-over-slf4j
> Currently it errors with the direct usage of the PropertyConfigurator in o.a.c.thrift.CassandraDaemon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message