Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@www.apache.org Received: (qmail 88056 invoked from network); 3 Nov 2004 00:46:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Nov 2004 00:46:43 -0000 Received: (qmail 7882 invoked by uid 500); 3 Nov 2004 00:46:40 -0000 Delivered-To: apmail-jakarta-lucene-dev-archive@jakarta.apache.org Received: (qmail 7816 invoked by uid 500); 3 Nov 2004 00:46:39 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 7802 invoked by uid 99); 3 Nov 2004 00:46:39 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of janssen@parc.com designates 13.1.64.93 as permitted sender) Received: from [13.1.64.93] (HELO alpha.xerox.com) (13.1.64.93) by apache.org (qpsmtpd/0.28) with SMTP; Tue, 02 Nov 2004 16:46:37 -0800 Received: from synergy1.parc.xerox.com ([13.1.101.60]) by alpha.xerox.com with SMTP id <174375(1)>; Tue, 2 Nov 2004 16:46:19 PST Received: from parc.com ([127.0.0.1]) by synergy1.parc.xerox.com with SMTP id <58617>; Tue, 2 Nov 2004 16:46:18 PST To: "Lucene Developers List" Subject: 1.4.2 breaks NewMultiFieldQueryParser by re-writing args list of getFieldQuery() Date: Tue, 2 Nov 2004 16:46:11 PST From: Bill Janssen Message-Id: <04Nov2.164618pst."58617"@synergy1.parc.xerox.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N It looks like 1.4.2 quietly broke the API exported by 1.4.1, which my NewMultiFieldQueryParser depended on. In particular, the Analyzer argument to getFieldQuery disappeared. Now, you folks shouldn't do this in a micro-release. Just add the new method, without removing the old one. And, if you do do it, you should note it in the CHANGES.txt file. And, if you do do it, you should have a way of detecting which version of Lucene is being used, so that developers can cope at configure time. Is there such a way? An easy command-line test to tell the 1.4.1 jar file from the 1.4.2 jar file? Bill --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-dev-help@jakarta.apache.org