Return-Path: Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org Received: (qmail 44753 invoked from network); 21 Aug 2009 15:39:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Aug 2009 15:39:30 -0000 Received: (qmail 36389 invoked by uid 500); 21 Aug 2009 15:39:52 -0000 Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org Received: (qmail 36338 invoked by uid 500); 21 Aug 2009 15:39:52 -0000 Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-dev@lucene.apache.org Received: (qmail 36328 invoked by uid 99); 21 Aug 2009 15:39:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2009 15:39:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yseeley@gmail.com designates 209.85.219.222 as permitted sender) Received: from [209.85.219.222] (HELO mail-ew0-f222.google.com) (209.85.219.222) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2009 15:39:43 +0000 Received: by ewy22 with SMTP id 22so794581ewy.28 for ; Fri, 21 Aug 2009 08:39:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=qt33iHR81KuHtXtNhBqBH3tSlvL9ydE31R62Ng5znxA=; b=E927b7oJ/lOHZ1tmEdd9FzQLQLzoUc37Ui8cObXd/WtjErx11N7onMdWuCHDnACXgE IKeh92hxfQVE8Nd97jrFJtDJhicXPu4kOg3Z948t9U9B1/7GTO1yNtcJiszqgfDYkyBx EdA+lcJTl6U6EmCScCMOWRs+7l2vrP8GXurR4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=TMjtNwhmLdJyDZYb2grQpcICarvr0VVrP1khWnftHlV1QQ0MLNLhEqm+4q4owVPkGW cUcawoj7weX3B8iwyyppgHkcEeG6yWfRj5DcMqPYq464b77+TcF8Pry8GagDSa3/jFZ/ kkiI5C/4DAdfjdghklRgcHiD5kNqTNsCjw3/g= MIME-Version: 1.0 Sender: yseeley@gmail.com Reply-To: yonik@lucidimagination.com Received: by 10.216.11.82 with SMTP id 60mr240820wew.36.1250869162221; Fri, 21 Aug 2009 08:39:22 -0700 (PDT) In-Reply-To: <176776ee0908210713s31981805k9dadf0eea57a1488@mail.gmail.com> References: <176776ee0908210713s31981805k9dadf0eea57a1488@mail.gmail.com> Date: Fri, 21 Aug 2009 11:39:22 -0400 X-Google-Sender-Auth: 3b23d4a4afdfacdf Message-ID: Subject: Re: /trunk ClassCastException with BaseTokenizerFactory From: Yonik Seeley To: solr-dev@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Fri, Aug 21, 2009 at 10:13 AM, Ryan McKinley wrote: > I'm fine upgrading, but it seems we should the 'back compatibility' > notice more explicit. Yeah... that should be fun for expert-use plugins in general. In Lucene-land, this is the release of the "break"... I think we've covered the changes reasonably well in our external APIs, but people can always use pretty much the full Lucene API when writing Solr plugins. I think we'll need to document that things in tags need to inherit from Tokenizer classes. It is technically a back-compat break, but I assume it will affect very few users? -Yonik http://www.lucidimagination.com