[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444500#comment-13444500
]
Uwe Schindler commented on LUCENE-4337:
---------------------------------------
bq. Actually you know what, I think I just talked myself out of my approach,
yes its a bit more generic but maybe its less transparent to people that dont
spend their time reading JVM source code, at least the policy file is more
obvious to those who are approaching this for the first time.
I also spend my time in reading JDK source code today! But it was more when
fixing Solr test violations (die, JMX/RMI, die, die, die).
> Create Java security manager for forcible asserting behaviours in testing
> -------------------------------------------------------------------------
>
> Key: LUCENE-4337
> URL: https://issues.apache.org/jira/browse/LUCENE-4337
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 4.1, 5.0, 4.0
> Reporter: Greg Bowyer
> Assignee: Greg Bowyer
> Attachments: ChrootSecurityManager.java,
> ChrootSecurityManagerTest.java, LUCENE-4337.patch, LUCENE-4337.patch,
> LUCENE-4337.patch
>
>
> Following on from conversations about mutation testing, there is an interest
> in building a Java security manager that is able to assert / guarantee
> certain behaviours
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
