[jira] Commented: (CASSANDRA-803) remove PropertyConfigurator from CassandraDaemon

["Carsten Krebs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903827#action_12903827 ] 

Carsten Krebs commented on CASSANDRA-803:
-----------------------------------------

As far I can see, the {{PropertyConfigurator}} is already removed with rev 934505 for CASSANDRA-971 .
Though {{org.apache.cassandra.service.StorageService#setLog4jLevel}} has another dependency to _log4j_, which will probably cause the same problems when using _log4j-over-sl4j_.
I don't know how to cope with this. What's the strategy  regarding the log4j dependencies? 
* Should all log4j dependencies be removed from the cassandra code base and thus in turn {{org.apache.cassandra.service.StorageServiceMBean#setLog4jLevel}} and all of it's implementations
* {{setLog4jLevel}} should be kept, but as some kind of optional operation, just in the case that log4j is present
* Stay completely with  log4j?
 



> 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.