[jira] [Commented] (SOLR-12987) Log deprecation warnings to separate log file

["David Smiley (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-12987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194596#comment-17194596 ] 

David Smiley commented on SOLR-12987:
-------------------------------------

I like the idea of DeprecationLogger but think a warning to the standard destinations is sufficient (no new file).

> 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
>          Components: logging
>            Reporter: Jan Høydahl
>            Priority: Major
>
> 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org