What should I care about JDK 9 module system?

on YouTube ↗23m

" summary

Migration testing using jdeps from JDK9 surfaces dozens of broken library uses of removed internals (example: sun.misc.BASE64Encoder), requiring either vendor fixes or local shims; running on JDK9 classpath often fails until those are fixed. Converting to modules reveals hundreds of split packages across a 20-year codebase that prevent module startup. A homegrown split-package scanner and running apps with --add-opens/--permit-illegal-access help triage, but fixes are needed for modules to work reliably.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 0:50Agenda
3. 1:48What can go wrong
4. 2:22Use some internals
5. 7:35Reflection
6. 9:57Summary
7. 13:04Warning
8. 13:50Split packages
9. 16:04Side note
10. 18:00Links

" related talks

• 49mModular Development with JDK 9Alex Buckley · Oracle OpenWorld 2017
• 49mTo JAR Hell And Back - A Live Migration to the Java 9 Module SystemNicolai Parlog · Jfokus 2018
• 51mModular Development with JDK 9Alex Buckley · Devoxx Belgium 2017
• 46mModular Development with JDK 9 and BeyondAlex Buckley · Oracle Code One 2018
• 53mModular Development with JDK 9Alex Buckley · Devoxx US 2017
• 47mJDK 9, 10, and 11: Pitfalls for the UnwarySimon Ritter · Oracle Code One 2018
• 45mPrepare for JDK 9Alan Bateman · Devoxx Belgium 2017
• 46mJDK 9, 10 and 11: Pitfalls For The UnwarySimon Ritter · Jfokus 2019