[
https://issues.apache.org/jira/browse/LUCENE-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425699#comment-13425699
]
Yonik Seeley commented on LUCENE-4276:
--------------------------------------
bq. what good can come from allowing someone to force lucene to run on 1.7.0?
This makes no sense to me.
This is indicative of the larger problem in Lucene development recently - the
tendency to prohibit something just because you can't think of the use-case off
the top of your head.
So here's your use-case: one *can* normally get most versions of most major
JVMs to correctly run applications - it's often just a matter of disabling
certain optimisations for certain methods, or in extreme cases prohibiting JIT
of the method altogether.
Hence, at a minimum, there should be a way for users to easily override this
behavior w/o recompiling applications. We should inform, not enforce.
> 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
>
> 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]
