Filed as LUCENE-4829 - Tokenizer and char and token filter subclasses are
not listed in Javadoc for the parent abstract classes.
https://issues.apache.org/jira/browse/LUCENE-4829
-- Jack Krupansky
-----Original Message-----
From: Steve Rowe
Sent: Tuesday, March 12, 2013 6:58 PM
To: [email protected]
Subject: Re: Javadoc "bug" for Lucene TokenFilter
On Mar 12, 2013, at 6:43 PM, "Jack Krupansky" <[email protected]>
wrote:
Thanks, Steve. I'm sure your response does in fact explain precisely why
the Lucene Javadoc is "failing" to live up to my expectation (i.e., that
all the actual tokenizers and filters are packaged as a separate
"module".)
But... I would note the package for LowerCaseFilter is
org.apache.lucene.analysis.core (yes, "core"), which is a parent package
of the package for TokenFilter, org.apache.lucene.analysis, so how does
your explanation of "optional" packages square with classes that are
clearly packaged as... "core"?
Another way of putting it is that the Tokenizer, TokenFilter, CharFilter,
and Analyzer classes are all "abstract", so how can the concrete classes
in any way be considered completely "optional"??
Lucene is a set of libraries, not an application?
It seems perfectly reasonable to me that some users might only need the core
library, and use analysis components of their own instead of those from the
Lucene analysis modules.
FWIW, my IDE (IntelliJ) is good at showing me all Tokenizer (etc.)
subclasses across the whole Lucene/Solr project. If yours doesn't, maybe
you should "switch"?
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
