You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Kenny MacLeod (JIRA)" <ji...@apache.org> on 2008/01/13 00:31:34 UTC
[jira] Commented: (LUCENE-685) Extract interface from IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558315#action_12558315 ]
Kenny MacLeod commented on LUCENE-685:
--------------------------------------
Interfaces in APIs are hard to manintain... you *are* kidding, right? Take a look at every well-written Java API out there, they *all* make heavy use of interfaces, because it makes API maintenance *easier*.
Never mind. Now that Spring has a Lucene API wrapper, I can use that to get a usable API.
> Extract interface from IndexWriter
> ----------------------------------
>
> Key: LUCENE-685
> URL: https://issues.apache.org/jira/browse/LUCENE-685
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.0.0
> Reporter: Kenny MacLeod
> Priority: Minor
> Attachments: InterfaceIndexWriter.java
>
>
> org.apache.lucene.index.IndexWriter should probably implement an interface to allow us to more easily write unit tests that use it. As it stands, it's a complex class that's hard to stub/mock.
> For example, an interface which had methods such as addDocument(), close() and optimize().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org