You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Grant Ingersoll (JIRA)" <ji...@apache.org> on 2008/01/13 00:22:34 UTC

[jira] Resolved: (LUCENE-685) Extract interface from IndexWriter

     [ https://issues.apache.org/jira/browse/LUCENE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Ingersoll resolved LUCENE-685.
------------------------------------

    Resolution: Won't Fix

Interfaces are hard to maintain from an API perspective and we have _generally_ concluded that we should avoid them given Lucene's backward-compatibility requirements.

> 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