[jira] [Closed] (LUCENENET-436) Refactor Deprecated Code inside of tests

["Laimonas Simutis (JIRA)" <ji...@apache.org>]

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

Laimonas Simutis closed LUCENENET-436.
--------------------------------------
    Resolution: Won't Fix

This seems like an outdated ticket that has not had activity for eight years. Lucene 4.8 goal should be to get released without deviating from the original code as much as possible due to our limited resources.

> Refactor Deprecated Code inside of tests 
> -----------------------------------------
>
>                 Key: LUCENENET-436
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-436
>             Project: Lucene.Net
>          Issue Type: Sub-task
>          Components: Lucene.Net Test
>    Affects Versions: Lucene.Net 2.9.4g, Lucene.Net 3.0.3
>            Reporter: michael herndon
>            Priority: Major
>              Labels: refactoring, testing,
>             Fix For: Lucene.Net 3.6
>
>
> * We should still be testing deprecated methods, but we need to use #pragma warning disable/enable 0618 for testing those. otherwise compiler warnings are too numerous to be anywhere near helpful.
> * We should only be using deprecated methods in places where they are being explicitly tested, other tests that need that functionality in 
> order to validate those tests should be re factored to use methods that are not deprecated.
> This is one place we should probably deviate from the parent project and make sure that any deprecated code gets isolated to the tests designed only for the deprecated methods and then use the newer API through out the testsuite.
> This should help move the project forward and remove deprecated API's when the time comes.   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)