[
https://issues.apache.org/jira/browse/LUCENE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443501#comment-13443501
]
Dawid Weiss commented on LUCENE-4332:
-------------------------------------
bq. Well if its for test purposes only and not enforcing actual security, we
should be able to give the runner a nice backdoor (e.g. static boolean
BACKDOORED) if we really need to right?
I don't know what it will do and how it will fail. I never run with a security
manager, I think the design of SM is complex, weird and poorly documented (as
evidenced by the security vuln. published today...). I just don't think of it
much because I know very few people that actually run with a SM enabled. I am
fairly sure I do many things in the code that I know won't work with an
installed SM -- scanning properties, opening files, etc. I'm sure it is
possible to configure it do grant permissions to certain packages but I've no
idea how to do it.
I'm not saying no to the idea, but I'm just letting you know that things may
break in unexpected ways and I will have limited time to learn SM internals...
Not that I'm especially looking forward to that. :)
> 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
>
>
> 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]
