temporary logging settings

Author: Bouncheck

driver-core/src/test/resources/log4j.properties

@@ -31,9 +31,9 @@ log4j.logger.spray.can=ERROR
 #log4j.logger.org.scassandra.http.client=ERROR
 
 # These loggers can be quite verbose
-log4j.logger.com.datastax.driver.core=INFO
-log4j.logger.com.datastax.driver.core.Cluster=ERROR
-log4j.logger.com.datastax.driver.core.policies.DCAwareRoundRobinPolicy=ERROR
+log4j.logger.com.datastax.driver.core=DEBUG
+#log4j.logger.com.datastax.driver.core.Cluster=ERROR
+#log4j.logger.com.datastax.driver.core.policies.DCAwareRoundRobinPolicy=ERROR
 
 # Useful loggers when debugging core functionality
 #log4j.logger.com.datastax.driver.core.ControlConnection=ERROR
@@ -44,7 +44,7 @@ log4j.logger.com.datastax.driver.core.policies.DCAwareRoundRobinPolicy=ERROR
 # Adjust log levels for CCM tests
 #log4j.logger.com.datastax.driver.core.CCMTestsSupport=DEBUG
 #log4j.logger.com.datastax.driver.core.CCMCache=DEBUG
-#log4j.logger.com.datastax.driver.core.CCMBridge=DEBUG
+log4j.logger.com.datastax.driver.core.CCMBridge=DEBUG
 
 # A1 is set to be a ConsoleAppender.
 log4j.appender.A1=org.apache.log4j.ConsoleAppender