You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Troy Howard (JIRA)" <ji...@apache.org> on 2011/02/21 18:55:38 UTC

[Lucene.Net] [jira] Updated: (LUCENENET-378) Objects with a Close method should support IDisposable

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

Troy Howard updated LUCENENET-378:
----------------------------------

         Due Date: 28/Mar/11
         Priority: Critical  (was: Major)
    Fix Version/s:     (was: Lucene.Net 3.x)
                   Lucene.Net 2.9.4

Scheduled for 2.9.4 release. 

This particular issue is too significant for .NET use cases, that leaving it for a 3.X release would take too long. 

This will involve a significant level of change to the source, tests, and demos. This should be implemented to be *backwards compatible* with standard Java API, but also allow use with IDisposable constructs.  

> Objects with a Close method should support IDisposable
> ------------------------------------------------------
>
>                 Key: LUCENENET-378
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-378
>             Project: Lucene.Net
>          Issue Type: Improvement
>          Components: Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test
>         Environment: .NET
>            Reporter: Kelly Elias
>            Priority: Critical
>             Fix For: Lucene.Net 2.9.4
>
>
> It would be very useful to have objects such as IndexSearcher and Directory support IDisposable. Then users can use "using" blocks to manage the lifespan of the objects and don't need to worry about accidentally leaving such objects open.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira