[ 
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448235#comment-13448235
 ] 

Greg Bowyer commented on LUCENE-4332:
-------------------------------------

Pitest forks surrogate runner jvms, when these things bootup they do some 
socket related nonsense for communication (SecurityPermission), and set on 
thread time monitoring (ManagementPermission)

SecurityPermission hides out in lots of strange places, one of these is in the 
DNS cache internal to a JVM.

We could restrict it, I didn't for ease of configuration since the security 
manager is aimed at preventing none malicious mistakes (like writing outside of 
the sandbox) rather than as a full force prevention of malicious code (which 
would require a bit more thinking through IMHO)
                
> Integrate PiTest mutation coverage tool into build
> --------------------------------------------------
>
>                 Key: LUCENE-4332
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4332
>             Project: Lucene - Core
>          Issue Type: Improvement
>    Affects Versions: 4.1, 5.0
>            Reporter: Greg Bowyer
>            Assignee: Greg Bowyer
>              Labels: build
>         Attachments: 
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch, 
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch, 
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch, 
> LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch
>
>
> As discussed briefly on the mailing list, this patch is an attempt to 
> integrate the PiTest mutation coverage tool into the lucene build

--
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]

Reply via email to