[
https://issues.apache.org/jira/browse/SOLR-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256689#comment-13256689
]
Steven Rowe commented on SOLR-3358:
-----------------------------------
{quote}
My IntelliJ is complaining about compiling Log4jWatcher. I think its because of
the classpath collision of the log4j and log4j-over-slf4j jars. Both include a
org.apache.log4j.LogManager and org.apache.log4j.spi.LoggingEvent, yet they
aren't the same classes. Any thoughts here? I'm not sure we can have the jars
as they are.
{quote}
Ant compilation succeeds only because {{log4j}} is ordered before
{{log4j-over-slf4j}} in the classpath. This is bad.
> 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-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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
