[
https://issues.apache.org/jira/browse/SOLR-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256796#comment-13256796
]
Ryan McKinley commented on SOLR-3358:
-------------------------------------
log4j implementation pulled out in r1327608
Let me know if you want me to pull out the whole thing...
bq. This will be a pain for all WAR users
Note the .war does not include log4j.jar
The aim is to provide a log4j implementation that can be used *if* the end user
implements logging with log4j.
Again, I am happy to put this elsewhere, but given that log4j is pretty common
it would be nice to make it work out-of-the-box
The first question is if we want to support log4j out of the box.
If so, I think the right approach is to add a new lib folder to webapp and put
all the slf4j-over .jar files in there
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
