Jan Høydahl created SOLR-12987:
----------------------------------
Summary: Log deprecation warnings to separate log file
Key: SOLR-12987
URL: https://issues.apache.org/jira/browse/SOLR-12987
Project: Solr
Issue Type: New Feature
Security Level: Public (Default Security Level. Issues are Public)
Components: logging
Reporter: Jan Høydahl
As discussed in solr-user list:
{quote}When instructing people in what to do before upgrading to a new version,
we often tell them to check for deprecation log messages and fix those before
upgrading. Normally you'll see the most important logs as WARN level in the
Admin UI log tab just after startup and first use. But I'm wondering if it also
makes sense to introduce a separate DeprecationLogger.log(foo) that is
configured in log4j2.xml to log to a separate logs/deprecation.log to make it
easier to check this from the command line. If the file is non-empty you have
work to do :)
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
