-
Task
-
Resolution: Fixed
-
P2
-
None
-
b41
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8082019 | emb-9 | Chris Hegarty | P2 | Resolved | Fixed | b41 |
In summary, the JDK and JRE images that we know today will change to be modular images. The resulting modular image that is the equivalent of the JDK will not have a top-level jre directory. Neither image will have rt.jar or tools.jar, these will be replaced with a new artifact/format that is being developed for modules and fast loading. Modular images will be created in the build by invoking an initial form of the jlink tool.
- backported by
-
JDK-8082019 Modular Run-Time Images
- Resolved
- blocks
-
JDK-8061971 JEP 220: Modular Run-Time Images
- Closed
- csr of
-
CCC-8049367 Modular Run-Time Images
- Closed
- relates to
-
CODETOOLS-7900981 Update jtreg to work with modular image
- Resolved
-
JDK-8146718 jdk/internal/jimage tests listed in both tier 1 and tier 2
- Resolved
-
JDK-8226928 [TESTBUG] test/java/net/NetworkInterface/IPv4Only.java fails intermittently on AIX
- Resolved
-
JDK-8067001 DetectMutableStaticFields fails after modular images push
- Closed
-
JDK-8049376 Move user-editable configuration files to top-level conf directory
- Resolved
-
JDK-8148969 Reorganize FX SDK layout to match JDK 9 layout
- Resolved
-
JDK-8065734 Build instructions for copying db to images have conflicting non-dependent targets
- Resolved
-
JDK-8068686 Remove meta-index support
- Closed
-
JDK-8153229 JavacFiler.checkFileReopening drowns in exceptions after Modular Runtime Images change
- Closed