lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <>
Subject Re: Please make org.apache.lucene.index.IndexWriter non-final
Date Sun, 05 Oct 2003 13:15:24 GMT

I disagree with your request to change things just for testing 
purposes.  There are ways to test most (if not all) of Lucene without 
having to affect method/class access levels.  As big as I am into 
testing, I'm also big into using the right design for the right job.  
In the case of Lucene, 'final' is used liberally as well as other 
non-public access levels.

Could you give us an example of what you're trying to test and how 
you're wishing you could go about it so that we could perhaps offer 

Look at Lucene's current codebase.  I've added a couple of mock objects 
recently to test various things - maybe that could give you some ideas?


On Sunday, October 5, 2003, at 05:09  AM, Mike Hogan wrote:

> Hi,
> Please can you make org.apache.lucene.index.IndexWriter non-final.  
> It's
> being final makes it impossible for me to test using mock objects.  
> Also, if
> there are other public final classes that are significant to the 
> Lucene API,
> please make them non-final also, for the same reason.
> One more thing, I see that there are cvs commits on the Lucene 
> project, but
> no releases in a long while.  What is the status with repect to new
> releases?  (In other words, if you do go ahead and make these classes
> non-final, when can I expect to be able to make use of the changes :)).
> Thanks,
> Mike.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message