-
Bug
-
Resolution: Fixed
-
P4
-
11, 12, 13
-
b30
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8217818 | 13 | Christoph Langer | P4 | Resolved | Fixed | b06 |
JDK-8218362 | 12.0.2 | Christoph Langer | P4 | Resolved | Fixed | b01 |
JDK-8218314 | 12.0.1 | Christoph Langer | P4 | Resolved | Fixed | b06 |
JDK-8219371 | 11.0.4-oracle | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8217890 | 11.0.3 | Christoph Langer | P4 | Resolved | Fixed | master |
Currently, the test test/jdk/java/net/Socket/ExceptionText.java implicitly tests for the default value of java.security's property jdk.includeInExceptions. The value should be null. I'd like to move this part of the test to an own test case in the jdk/security/JavaDotSecurity path.
This will ease maintenance of tests in case the default value is changed (e.g. forks of the OpenJDK or different build configurations).
This will ease maintenance of tests in case the default value is changed (e.g. forks of the OpenJDK or different build configurations).
- backported by
-
JDK-8217818 Move the test for default value of jdk.includeInExceptions into own test
-
- Resolved
-
-
JDK-8217890 Move the test for default value of jdk.includeInExceptions into own test
-
- Resolved
-
-
JDK-8218314 Move the test for default value of jdk.includeInExceptions into own test
-
- Resolved
-
-
JDK-8218362 Move the test for default value of jdk.includeInExceptions into own test
-
- Resolved
-
-
JDK-8219371 Move the test for default value of jdk.includeInExceptions into own test
-
- Resolved
-