[
https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425755#comment-13425755
]
Robert Muir commented on LUCENE-4276:
-------------------------------------
{quote}
Can we include some text in the message, describing why it's incompatible, such
as a link to a JIRA issue / markmail thread?
{quote}
We can, ideally we would link to the original bugs, but they are now hidden
from view in Oracle's issue tracker as this was related to some security
vulnerabilities.
We could also link to http://vimeo.com/33817739 :)
{quote}
How do you know to recommend a specific build version?
{quote}
Because 1.7.0_01 was a bugfix release addressing this issue (broken loop
optimizations).
I don't mind listing that "Oracle Corporation" 1.7.0 is broken and not
suggesting a version to upgrade to though, I think thats fine.
> refuse to execute on broken corrupting jvms
> -------------------------------------------
>
> Key: LUCENE-4276
> URL: https://issues.apache.org/jira/browse/LUCENE-4276
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Blocker
> Fix For: 4.0
>
> Attachments: LUCENE-4276.patch
>
>
> There are some jvms where we know lucene does not work at all and will just
> produce things like corrupt indexes.
> We should detect this in a static block of Constants.java and refuse to run
> at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
