: Since it is advanced not really public API stuff, it seems a bit cleaner to
: just delete.
:
: Adding another to the TON of deprecated classes seems OK too...
if we want to follow hte precendent set by Lucene-Java, code that compiles
against X.Y needs to be able to compile against X.Y+N ... s
Mike Klaas wrote:
Core request handlers do not use this, favouring the new,
almost-identical code in the highlighting package. Deprecate or
delete? It is rather simple to upgrade code using this to the new regime.
Either way is fine by me.
Since it is advanced not really public API stuff,
Core request handlers do not use this, favouring the new, almost-
identical code in the highlighting package. Deprecate or delete? It
is rather simple to upgrade code using this to the new regime.
-Mike
