-
Bug
-
Resolution: Fixed
-
P4
-
9, 12
-
b15
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8256191 | 11.0.11-oracle | Dukebot | P4 | Resolved | Fixed | b01 |
JDK-8258608 | 11.0.11 | Alan Bateman | P4 | Resolved | Fixed | b01 |
For module M1 and M2, mapped to class loaders L1 and L2: if M1 reads M2 then L1 needs to delegate to L2 to load classes in packages that M2 exports to M1. The class loader(s) created by ModuelLayer defineModulesWithXXX do not setup this delegation correctly for the case that M2 is an automatic module and L1 != L2.
The issue was reported on the jigsaw-dev list here:
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2018-October/013971.html
The issue was reported on the jigsaw-dev list here:
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2018-October/013971.html
- backported by
-
JDK-8256191 ModuleLayer.defineModulesWithXXX does not setup delegation when module reads automatic module
- Resolved
-
JDK-8258608 ModuleLayer.defineModulesWithXXX does not setup delegation when module reads automatic module
- Resolved