lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Updated] (LUCENE-3239) drop java 5 "support"
Date Thu, 30 Jun 2011 12:08:28 GMT


Simon Willnauer updated LUCENE-3239:

    Attachment: LUCENE-3239.patch

here is a patch that fixes almost all todos except of the one in NativeFSLock. I think for
that we should open a sep. issue. I didn't convert all the ArrayUtils yet I think we can do
that later in a followup too. 

> drop java 5 "support"
> ---------------------
>                 Key: LUCENE-3239
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Robert Muir
>         Attachments: LUCENE-3239.patch, LUCENE-3239.patch
> its been discussed here and there, but I think we need to drop java 5 "support", for
these reasons:
> * its totally untested by any continual build process. Testing java5 only when there
is a release candidate ready is not enough. If we are to claim "support" then we need a hudson
actually running the tests with java 5.
> * its now unmaintained, so bugs have to either be hacked around, tests disabled, warnings
placed, but some things simply cannot be fixed... we cannot actually "support" something that
is no longer maintained: we do find JRE bugs (
and its important that bugs actually get fixed: cannot do everything with hacks.
> * because of its limitations, we do things like allow 20% slower grouping speed. I find
it hard to believe we are sacrificing performance for this.
> So, in summary: because we don't test it at all, because its buggy and unmaintained,
and because we are sacrificing performance, I think we need to cutover the build system for
the next release to require java 6.

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message