I've no opinion on the respective merits of logging frameworks but not having the choice causes deployment difficulties. IMHO, the core issue is that JUL configuration is container dependant (Tomcat JULI allows per-webapp logging.properties configuration, what about Websphere ?), not application/war dependant which is more convenient/generic.
I've posted https://issues.apache.org/jira/browse/SOLR-549 SOLR-549 that preserves the JUL choice as an API but adds/refactors some code so the application packaging can choose what to do. But doing this is not really different than switching to another logging API (slf4j rather than commons if we go that way). -- View this message in context: http://www.nabble.com/Solr-Logging-tp16836646p16847799.html Sent from the Solr - Dev mailing list archive at Nabble.com.
