[
https://issues.apache.org/jira/browse/SOLR-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256710#comment-13256710
]
Robert Muir commented on SOLR-3358:
-----------------------------------
hmm, 4 logging jars, excluding certain jars for different things here and there,
this creates a lot of complexity and dependency management.
log4j-over-slf4j already has the log4j api, it must for it to work
(http://www.slf4j.org/legacy.html)
so I don't understand why the log4j jar is being added! Why is this necessary?
If we are going to add log4j, then slf4j should removed,
otherwise the whole purpose of a logging facade is defeated.
One of these must go.
> Capture Logging Events from JUL and Log4j
> -----------------------------------------
>
> Key: SOLR-3358
> URL: https://issues.apache.org/jira/browse/SOLR-3358
> Project: Solr
> Issue Type: New Feature
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Attachments: SOLR-3358-compile-path.patch, SOLR-3358-logging.patch,
> SOLR-3358-logging.patch
>
>
> The UI should be able to show the last few log messages. To support this, we
> will need to register an Appender (log4j) or Handler
> (JUL) and keep a buffer of recent log events.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
