On 11/8/2018 6:06 AM, Jan Høydahl wrote:
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 :)
+1
I think we need to leave additivity set to true on this one so that the
logs are duplicated in solr.log. Perhaps explicitly set additivity to
true in the config so that it's easy for somebody to disable it if it's
important to them to not have log duplication.
I have an implementation question, but that can wait until there's an
issue in Jira.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
