-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b27
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8299293 | 17.0.7-oracle | Prasadarao Koppula | P3 | Resolved | Fixed | b01 |
JDK-8299797 | 17.0.7 | Severin Gehwolf | P3 | Resolved | Fixed | b01 |
JDK-8312009 | 11.0.21-oracle | Ramesh Gangadhar | P3 | Resolved | Fixed | b03 |
JDK-8299869 | 11.0.19 | Severin Gehwolf | P3 | Resolved | Fixed | b01 |
JDK-8308889 | openjdk8u382 | Severin Gehwolf | P3 | Resolved | Fixed | b03 |
It illustrates that having -Djava.locale.providers=SPI with a custom CalendarDataProvider and any signed JAR in the classpath is enough to trigger the problem as described in
- backported by
-
JDK-8299293 Add a regression test for JDK-8297684
-
- Resolved
-
-
JDK-8299797 Add a regression test for JDK-8297684
-
- Resolved
-
-
JDK-8299869 Add a regression test for JDK-8297684
-
- Resolved
-
-
JDK-8308889 Add a regression test for JDK-8297684
-
- Resolved
-
-
JDK-8312009 Add a regression test for JDK-8297684
-
- Resolved
-
- relates to
-
JDK-8298271 java/security/SignedJar/spi-calendar-provider/TestSPISigned.java failing on Windows
-
- Resolved
-
-
JDK-8280890 Cannot use '-Djava.system.class.loader' with class loader in signed JAR
-
- Closed
-
-
JDK-8297684 NullPointerException in JarVerifier prevents JVM from starting
-
- Closed
-
-
JDK-8269039 Disable SHA-1 Signed JARs
-
- Closed
-
- links to
-
Commit openjdk/jdk8u-dev/29ba98e5
-
Commit openjdk/jdk11u-dev/03555b11
-
Commit openjdk/jdk17u-dev/8a8cdeb7
-
Commit openjdk/jdk/4da84116
-
Review openjdk/jdk8u-dev/269
-
Review openjdk/jdk11u-dev/1608
-
Review openjdk/jdk17u-dev/977
-
Review openjdk/jdk/11515