r-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
_
From: Shai Erera [mailto:ser...@gmail.com]
Sent: Sunday, November 22, 2009 12:06 PM
To: java-dev@lucene.apache.org
Subject: Re: Problematic documentation in o.a.l.analysis.package.html
Perhaps copyTo works for
e whole attributes API.
>
>
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
> --
>
> *From:* Shai Erera [mailto:ser...@gmail.com]
> *Sent:* Sunday, No
AM
To: java-dev@lucene.apache.org
Subject: Re: Problematic documentation in o.a.l.analysis.package.html
Thanks Uwe.
About (3), I use copyTo, not clone. I used the word 'clone' just out of
habit. I'll read more about captureState, but I think copyTo works fine for
me.
Abour (2)
Thanks Uwe.
About (3), I use copyTo, not clone. I used the word 'clone' just out of
habit. I'll read more about captureState, but I think copyTo works fine for
me.
Abour (2), I still think it's confusing. When I read addAttribute, I get an
impression as if by calling this method, it is guaranteed
Hi Shai,
Thanks for the suggestions!
About your points:
1) This is really wrong, we can easily fix it for 3.1. Lucene 3.0 is
already in the vote phase and 2.9x is also already out.
2) Maybe the explanation is not so good. This text comes especially
from the 2.9 old to new TS