To JAR Hell And Back - A Live Migration to the Java 9 Module System
summary
Live migration of a Maven multi-module app to Java 9 reveals concrete breakage and fixes: use jdeps to find missing JDK modules, swap Sun internal APIs to java.util.Base64, and replace Java EE libs or add them with --add-modules; Mockito/ByteBuddy triggers illegal reflective access fixed with --add-opens or by updating libraries; split packages (jsr305 vs JDK) force using --patch-module or renaming/merging jars; application class loader stops being URLClassLoader so classloader casting breaks. Most fixes are runtime JVM flags or dependency upgrades; jlink creates slim images.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:24Public Service Announcement
- 3:11Module Declaration
- 3:53Reliable Configuration
- 6:56Other Features
- 9:57The Unnamed Module
- 33:15Split Packages
- 44:54Run-Time Images
related talks
48mTo JAR Hell And Back - A Live Migration to the Java 9
23mWhat should I care about JDK 9 module system?
49mModular Development with JDK 9
50mJDK 11: Pitfalls for the Unwary
46mModular Development with JDK 9 and Beyond
53mModular Development with JDK 9
51mModular Development with JDK 9
46mJDK 9, 10 and 11: Pitfalls For The Unwary
