The Lucene Javadoc for TokenFilter shows only a single Direct Known Subclass when in fact there are dozens of them. The Lucene JavaDoc for LowerCaseFilter does in fact show TokenFilter as it’s direct parent class even though the Javadoc for TokenFilter does not report LowerCaseFilter as a Direct Known Subclass.
Is this any good reason for this discrepancy, or is this simply a bug in either Lucene’s packaging or the javadoc generation? 4.0, 4.1, and 4.2 all have consistent behavior, but 3.6 reports a long list of the expected subclasses. I suspect it may have to do with the fact that the subclasses are off in a separate folder from the parent class. See: http://lucene.apache.org/core/4_1_0/core/org/apache/lucene/analysis/TokenFilter.html http://lucene.apache.org/core/4_1_0/analyzers-common/org/apache/lucene/analysis/core/LowerCaseFilter.html http://lucene.apache.org/core/3_6_0/api/all/org/apache/lucene/analysis/TokenFilter.html Note: The Lucene Javadoc for TokenFilterFactory does in fact show dozens of Direct Known Subclasses, as expected. -- Jack Krupansky
