[
https://issues.apache.org/jira/browse/LUCENE-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552118#comment-13552118
]
Robert Muir commented on LUCENE-4417:
-------------------------------------
Seems pretty complicated, core tests depend upon things like test-framework and
codecs, which have experimental APIs. (look at 4.0 codebase if you dont believe
me, whole experimental codecs have been folded into core functionality and
removed, and so on).
Even if we were to do this, i don't think it would be maintainable. For
example, take issues that will seriously change the codec API like LUCENE-4547.
I'd be the first to simply disable the whole thing rather than waste a bunch of
time fixing outdated tests and experimental codecs from a previous release.
I think it would be more bang for the buck to integrate an API comparison tool
(like jdiff or whatever) that shows the breaks so we know what they are.
> Re-Add the backwards compatibility tests to 4.1 branch
> ------------------------------------------------------
>
> Key: LUCENE-4417
> URL: https://issues.apache.org/jira/browse/LUCENE-4417
> Project: Lucene - Core
> Issue Type: Task
> Components: general/test
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Blocker
> Fix For: 4.1
>
>
> In 4.0 we have no backwards compatibility, but in 4.1 we must again
> ivy-retrieve the 4.0 JAR file and run the core tests again (like in 3.6). We
> may think about other modules, too, so all modules that must be backwards
> compatible should be added to this build.
> I will work on this once we have a release candidate in Maven Central.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
