lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Janssen <>
Subject How do Lucene applications deal with API changes?
Date Tue, 02 Nov 2004 16:54:31 GMT
Thanks to Bill Tschumy, who points out that Lucene 1.4.21 *breaks* the
API exported by 1.4 by removing a parameter from
QueryParser.getFieldQuery().  That means that my
NewMultiFieldQueryParser also breaks, since it overrides that method.
To fix, just remove the Analyzer parameter from the getFieldQuery()
method in NewMultiFieldQueryParser.

More generally, how is an application developer that wants to use
Lucene supposed to deal with these kinds of things?  It's a micro
release, the change isn't noted in the CHANGES.txt file, and as far as
I can see, there are no version numbers in the jar file you could look
at during an application "configure".

Does anyone have any successful ways of dealing with these kinds of
things?  The only thing I can think of is to put a specific Lucene jar
in my app source code.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message