[
https://issues.apache.org/jira/browse/LUCENE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558402#action_12558402
]
Grant Ingersoll commented on LUCENE-685:
----------------------------------------
Well, they are hard to maintain when you want to go add a new method and you
end up breaking 500 users who then flood the list b/c their implementations are
broken because of interface changes. So, in general, we favor abstract
classes. If Lucene had a different policy on back-compatibility, then this
could change.
At any rate, this issue is not for that discussion. I'd be happy to visit it
on java-dev, as I actually think it is an area Lucene could be better about.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
