Also, I am working on a change where the java.security.policy== option
will include the permissions granted to de-privileged modules [1]. So
once that is in, you will be able to use the '==' option instead.
--Sean
[1] https://bugs.openjdk.java.net/browse/JDK-8159752
On 07/13/2016 03:59 AM, Mandy Chung wrote:
On Jul 13, 2016, at 3:23 PM, Weijun Wang <weijun.w...@oracle.com> wrote:
On 7/8/2016 19:34, Sean Mullan wrote:
Use the new jtreg "java.security.policy=p" option. This will
concatentate the specified policy with the configured system policy files.
I've used this new option.
However, it also picks up ~/.java.policy, which I believe will bring in some
noise. Maybe jtreg can be enhanced to ignore ~/.java.policy?
IMO it’s a configuration issue. We should make sure ${java.home}/.java.policy
is not present when running the regression tests.
In addition, to ignore ${java.home}/.java.policy, it’s a change in the policy
file I believe (not in jtreg).
Mandy
