If we pick the latest, just let us use LUCENE_CURRENT. Its deprecated not because we want to remove it in future, we don’t want anybody to use it in normal code. For benchmark, simply add @SuppessWarnings(“deprecated”) at the place where the config file is parsed. J In Solr we do the same, if somebody uses LUCENE_CURRENT in the solrconfig.xml or on any tokenstream/analyzer.
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: u...@thetaphi.de From: Shai Erera [mailto:ser...@gmail.com] Sent: Wednesday, March 24, 2010 8:18 PM To: java-dev@lucene.apache.org Subject: Re: LUCENE_CURRENT in Benchmark I suppose we should allow it as an .alg parameter, so one can test the same algorithm on different versions. Also, if it's not specified, let's always pick the latest? Shai On Wed, Mar 24, 2010 at 7:19 PM, Grant Ingersoll <gsing...@apache.org> wrote: I see that Test has TEST_CURRENT_VERSION for version, but what about Benchmark? Seems we should be using the latest and greatest, but LUCENE_CURRENT is deprecated. -Grant --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
