[ https://issues.apache.org/jira/browse/LUCENENET-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Currens updated LUCENENET-436: ------------------------------------------ Affects Version/s: Lucene.Net 3.0.3 Fix Version/s: (was: Lucene.Net 3.0.3) Lucene.Net 3.5 > 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 > Labels: refactoring, testing, > Fix For: Lucene.Net 3.5 > > > * 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira