You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ryan McKinley (JIRA)" <ji...@apache.org> on 2013/03/15 09:00:19 UTC
[jira] [Resolved] (SOLR-3399) distribute/assume log4j logging
rather then JUL
[ https://issues.apache.org/jira/browse/SOLR-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley resolved SOLR-3399.
---------------------------------
Resolution: Duplicate
> distribute/assume log4j logging rather then JUL
> -----------------------------------------------
>
> Key: SOLR-3399
> URL: https://issues.apache.org/jira/browse/SOLR-3399
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
>
> The discussion on SOLR-3358 has many threads, so I will break this out in its own issue.
> Currently we use SLF4j to define logging and the war file distributes the the JUL binding. To improve the out-of-the-box logging experience, I think we should switch to log4j. I suggest we:
> * keep using SLF4J (especially in solrj)
> * replace the JUL log watcher with a log4j version
> * this will let us have the admin UI logging stuff work against a single Appender rather then the root loggers
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org