Hi Brad
I think I found a problem with the test. Before you set your local
java.security file, the system java.security file was already read (in
jtreg initialization) and limited was picked up. In fact, I modified the
java.security file of my own JDK to unlimited and the test fails.
This seems to show that we have to set the system property on the
command line. Either we provide a modified java.security with the test
like SeanM suggested, or we create it dynamically and manually launch a
new java process. I prefer the latter.
Thanks
Max
On 11/18/2016 1:46 AM, Bradford Wetmore wrote:
SeanM pointed out that we could do a:
@main -Djava.security.properties=xxx
but that would require storing a snapshot of java.security. I think I
prefer it being dynamically generated.
