[
https://issues.apache.org/jira/browse/SOLR-12987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205833#comment-17205833
]
ASF subversion and git services commented on SOLR-12987:
--------------------------------------------------------
Commit c41db675915129d9b749ff07a9d774f50e731bfc in lucene-solr's branch
refs/heads/branch_8x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c41db67 ]
SOLR-12987: Fix precommit
(cherry picked from commit 6c3b1aa5ca2cdaaa63be73fb5425fd3b372d40b4)
> 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
> Assignee: David Smiley
> Priority: Major
> Fix For: 8.7
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
