[
https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425771#comment-13425771
]
Yonik Seeley commented on LUCENE-4276:
--------------------------------------
bq. I didnt say I objected to the override completely,
The historical revisions are tiresome. How else is one supposed to interpret
this:
https://issues.apache.org/jira/browse/LUCENE-4276?focusedCommentId=13425710&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13425710
bq. It would be far far better to just detect if -XX:-UseLoopPredicate or -Xint
are set instead and not have a -Drisky.override.
No, we still need an override. We do not always know best.
> 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]
