- 
    Bug 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    9, 10
- 
        b10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8355718 | 8u471 | Shivangi Gupta | P4 | Resolved | Fixed | b01 | 
                    there is a couple issue w/ DoPrivAccompliceTest.java test:
- it's semi-automatic test, although it checks whether a spawn jvm exits gracefully, the test won't fail if it does not
- "negative" case is not covered. the test does not check that DoPrivTest.jar does not have rights to read 'user.home' property
- the test uses its own testlibrary to create a jar, start a jvm, while there is a common testlibrary for the same use cases.
- the test does not follow code style, it's hard to read it, especially createPolicyFile method.
- the test creates files in class files directory which can affect other tests results
- it's semi-automatic test, although it checks whether a spawn jvm exits gracefully, the test won't fail if it does not
- "negative" case is not covered. the test does not check that DoPrivTest.jar does not have rights to read 'user.home' property
- the test uses its own testlibrary to create a jar, start a jvm, while there is a common testlibrary for the same use cases.
- the test does not follow code style, it's hard to read it, especially createPolicyFile method.
- the test creates files in class files directory which can affect other tests results
- backported by
- 
                    JDK-8355718 java/security/AccessController/DoPrivAccompliceTest.java has to be improved -           
- Resolved
 
-         
- blocks
- 
                    JDK-8180898 remove JavaToolUtils testlibrary class -           
- Resolved
 
-