[
https://issues.apache.org/jira/browse/SOLR-17485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-17485:
----------------------------------
Labels: pull-request-available (was: )
> Remove Slf4j ClassNotFoundException avoidance checks
> ----------------------------------------------------
>
> Key: SOLR-17485
> URL: https://issues.apache.org/jira/browse/SOLR-17485
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a user removes logging libs from lib/ext, they are on their own, more or
> less. CheckLoggingConfiguration (SOLR-5951) tries to detect an early
> ClassNotFoundException and prints a more helpful error. IMO we're doing too
> much; a CNFE is clear enough, and furthermore Slf4j will print an explicit
> ERROR as well right before (what happens if we remove it; I tried). I
> suspect it came out when Solr still supported a WAR or maybe was less clear
> what the error was back then. And I suspect it hasn't worked since we added
> a ServletContextListener for CoreContainerProvider. While it could be
> remedied, I'd rather remove the old code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
