Hi Max,
I agree that sometimes use of a shell script makes a test clearer. On
the other hand, if we are trying to create pure Java tests, it increases
overall coverage of Java APIs.
I updated the tests to use ProcessTools, and simplified a little bit
policy files for negative tests to make them clearer. Please take a look:
http://cr.openjdk.java.net/~asmotrak/8048147/webrev.02/
Artem
On 03/18/2015 06:08 PM, Wang Weijun wrote:
On Mar 18, 2015, at 19:31, Artem Smotrakov <artem.smotra...@oracle.com> wrote:
The tests can be updated to start a new process with ProcessTools, or use a
script.
Choose anyone you like.
Maybe you can a few experiments to see what is the difference between a script
test and a Java test that launches processes.
I'm a little surprised that with the classpath not pointing to jars the test
still succeeds. The jars should have been granted different permissions. Maybe
the test is not designed smart enough to detect the problem?
--Max
Artem
