+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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
