[
https://issues.apache.org/jira/browse/SOLR-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507522#comment-13507522
]
David Smiley commented on SOLR-4129:
------------------------------------
I changed this issue to an "improvement" and changed the title to reflect it's
a UI thing. That is what is reflected in the patch. The author of the
description on the other hand, appears to be unaware that
log4j-over-slf4j-1.7.2.jar needs to be removed if you're going to log to Log4j.
I believe there's even an ant target to pre-package the .war file
appropriately.
> Solr UI doesn't support log4j
> ------------------------------
>
> Key: SOLR-4129
> URL: https://issues.apache.org/jira/browse/SOLR-4129
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0
> Reporter: Raintung Li
> Labels: log
> Fix For: 4.1, 5.0
>
> Attachments: patch-4129.txt
>
>
> For many project use the log4j, actually solr use slf logger framework, slf
> can easy to integrate with log4j by design.
> Solr use log4j-over-slf.jar to handle log4j case.
> This jar has some issues.
> a. Actually last invoke slf to print the logger (For solr it is
> JDK14.logging).
> b. Not implement all log4j function. ex. Logger.setLevel()
> c. JDK14 log miss some function, ex. thread.info, day rolling
> Some dependence project had been used log4j that the customer still want to
> use it. JDK14 log has many different with Log4j, at least configuration file
> can't reuse.
> The bad thing is log4j-over-slf.jar conflict with log4j. If use solr, the
> other project have to remove log4j.
> I think it shouldn't use log4j-over-slf.jar, still reuse log4j if customer
> want to use it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
