-
Bug
-
Resolution: Fixed
-
P3
-
17.0.2, 18, 19
-
b13
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8284244 | 18.0.2 | Tobias Hartmann | P3 | Resolved | Fixed | b02 |
JDK-8283821 | 17.0.4-oracle | Tobias Hartmann | P3 | Resolved | Fixed | b01 |
JDK-8283554 | 17.0.4 | Severin Gehwolf | P3 | Resolved | Fixed | b01 |
This used to work on the assumption that the internal class names didn't contain the . character and that java class names didn't contain the / character except for lambdas (which are now treated as hidden classes as well), an assumption that no longer holds.
- backported by
-
JDK-8283554 [JVMCI] MetaUtil.toInternalName() doesn't handle hidden classes correctly
- Resolved
-
JDK-8283821 [JVMCI] MetaUtil.toInternalName() doesn't handle hidden classes correctly
- Resolved
-
JDK-8284244 [JVMCI] MetaUtil.toInternalName() doesn't handle hidden classes correctly
- Resolved
- relates to
-
JDK-8238358 Implementation of JEP 371: Hidden Classes
- Resolved
- links to
-
Commit openjdk/jdk17u-dev/13140f91
-
Commit openjdk/jdk18u/e6c08ada
-
Commit openjdk/jdk/0cbc4b85
-
Review openjdk/jdk17u-dev/274
-
Review openjdk/jdk18u/87
-
Review openjdk/jdk/7346