On 17/11/2016 17:46, Bradford Wetmore wrote:
On 11/17/2016 7:19 AM, Seán Coffey wrote:
The /policy= jtreg tag was also another possible solution.
That's a policy file, not a java.security file.
Ah, of course. Wasn't thinking right.
regards,
Sean.
SeanM pointed out that we could do a:
On 11/17/2016 7:19 AM, Seán Coffey wrote:
The /policy= jtreg tag was also another possible solution.
That's a policy file, not a java.security file.
SeanM pointed out that we could do a:
@main -Djava.security.properties=xxx
but that would require storing a snapshot of java.security.
Looks good to me. I didn't know you could pass a plain file 'name' to
java.security.properties. The docs indicate that a URL is required but
the jdk code suggests your approach will work.
The /policy= jtreg tag was also another possible solution.
regards,
Sean.
On 17/11/2016 01:33, Bradford
Hello team,
Please review a small fix for security tests.
BugID: https://bugs.openjdk.java.net/browse/JDK-8169866
Web review: http://cr.openjdk.java.net/~skovalev/8169866/webrev.00/
Issue: Tests from package com/sun/security failing in case of usage
"--limit-modules java.base" command line
Looks good.
--Sean
On 11/15/16 9:55 PM, Wang Weijun wrote:
Please review the updated webrev at
http://cr.openjdk.java.net/~weijun/7004967/webrev.02/
Only spec change [1].
This change also covers 8169312.
Thanks
Max
[1]
