Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Developers List" <lucene-dev@jakarta.apache.org>
Message-ID: <3C761CFC.1010804@earthlink.net>
Date: Fri, 22 Feb 2002 03:27:08 -0700
From: Dmitry Serebrennikov <dmitrys@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.7) Gecko/20011221
MIME-Version: 1.0
To: Lucene Developers List <lucene-dev@jakarta.apache.org>
Subject: Re: can some access modifiers in  org.apache.lucene.search be
 changed/"opened up"
References: <728DA21B8941A843A7C496F1ACF485185AD25B@gleam.lumos.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

+1 on this. I was going to propose the same change by waited until the 
release went out.
While we are at this, can we also make the 
org.apache.lucene.analysis.PorterStemmer class public again? It is 
useful in case you want to utilize stemming in the same application 
where Lucene is being used. If the counterargument is that this confuses 
the purpose of the analysis package, perhaps PorterStemmer can be moved 
to util?

Dmitry


Spencer, Dave wrote:

>Proposed solution is to change a couple of decls in Scorer and Query:
>
>    Scorer.java
>	make score() public
>
>    Query.java
>      make all methods public or protected (normalize,
>sumOfSquaredWeights,prepare)
>
>By doing this other Queries can be added w/o having to be in the above
>package.
>Nothing can possibly break by doing it :) and I don't think this is a
>design/encapsulation
>flaw to expose these.
>
>So if there's no major objections by others or misunderstandings on my
>part
>could the powers of be make the above decl changes?
>
>Thanks,
>  Dave
>


--
To unsubscribe, e-mail:   <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>