Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <1184328822.14866.1199984061@webmail.messagingengine.com>
References: <758071.70810.qm@web23010.mail.ird.yahoo.com>
 <1184328822.14866.1199984061@webmail.messagingengine.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F016DF82-65A4-4988-B367-7A8EB5506047@apache.org>
Content-Transfer-Encoding: 7bit
From: Grant Ingersoll <gsingers@apache.org>
Subject: Re: Post mortem kudos for (LUCENE-843) :)
Date: Fri, 13 Jul 2007 08:59:01 -0400
To: java-dev@lucene.apache.org

This is good stuff...  Might be good to put a organized version of  
this up on the Wiki under Best Practices

On Jul 13, 2007, at 8:13 AM, Michael McCandless wrote:

>
> Yeah it's not so easy now: Field.java does not have setters.
>
> You have to make your own class that implements Fieldable (or
> subclasses AbstractField) and adds your own setters.  Field.java is
> also [currently] final so you can't subclass it.
>

Should we consider putting in these changes?  I think it might be a  
little weird on the Search side to have setters for Field and it  
sounds like it could cause trouble for people esp. in a threaded  
indexing situation, but maybe I am mistaken?

At any rate, it sounds like these would be good contributions as long  
as they are well documented.


-Grant


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org