lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McKinley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3358) Capture Logging Events from JUL and Log4j
Date Wed, 18 Apr 2012 17:28:40 GMT


Ryan McKinley commented on SOLR-3358:

bq. so I don't understand why the log4j jar is being added! Why is this necessary?

The log4j-over-slf4j.jar only wraps the calls to write events, it does not wrap anything for
handling events (Appender and LoggingEvent).  Ideally log4j would only be in the classpath

The point of this is to capture events if the end user binds JUL or Log4j.  Alternatively
I could put the log4j implementation elsewhere, but that seems kinda silly since lots of people
actually use log4j

> Capture Logging Events from JUL and Log4j
> -----------------------------------------
>                 Key: SOLR-3358
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message