lucene-dev mailing list archives

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


Robert Muir commented on SOLR-3358:

I strongly agree here with Robert, one thing to add: Maven (sorry) has the notion of "runtime",
"test" and "compile" (and even "test-compile") classpaths, which may all be different.

The parallel exists in ivy, its easy to use. its called configurations (we actually already
use these), and you can
name them whatever you want.

with such configurations we could even have things like test-classpath-jetty, test-classpath-tomcat,
test-classpath-log4j, whatever whatever.

We already use configurations (for a different purpose) in some of the solr ivy.xml's... 

If we wanted, i'm sure such a thing could be used to even e.g. implement lucene's test-backwards
and things like that
in the future. This is really a similar situation in many ways if you think about it...

> 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