[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444922#comment-13444922
]
Uwe Schindler commented on LUCENE-4337:
---------------------------------------
I tried that out but failed to do it, because the policy file was not able to
load the custom Permission at all (it must be signed maybe). It did not even
print a System.err inside a static {} block in the class!
I also think the current explicit permissions are much better to manage and we
know what our code needs (as we have to enable additional permissions when new
features are added).
> 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: [email protected]
For additional commands, e-mail: [email protected]
