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 19:16:39 GMT


Ryan McKinley commented on SOLR-3358:

yes, solr classpath is a disaster!  I agree with everything you say/suggest, i figured this
was the tradeoff for avoiding maven

The other thing to consider is a test classpath -- the only class that uses jetty in the src
tree is JettySolrRunner.  I think that could be moved to test.

re SpellChecker in solrj.  The maven build should fail if you do this since it does use different
classpaths for each module.  (not a real solution, but just pointing it out)

As a first step, I think we should remove the single solr/lib folder and replace it with:
 core/lib-test  (includes jetty)
 webapp/lib (has the slf4j-over stuff)

> 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