+1 Sounds like a good a idea to me. > On Nov 8, 2018, at 5:06 AM, Jan Høydahl <jan....@cominvent.com> wrote: > > Hi, > > 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 :) > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
