Panel Session - Modularity Futures: OSGi and Java 9+
summary
Discussion documents the current modularity reality: Java 9/10 are ephemeral, Java 11 is the first LTS and ships with the kill switch enabled by default so deep reflection still works, but true module enforcement remains off; many libraries lack module-info (attempts to measure adoption fail) and SLF4J 1.8 stalls. Tooling only covers basics (Maven/Gradle pass-throughs, custom build hacks for multi-release jars). JLink and bundle analysis are used to shrink runtimes — an Open Liberty example goes from ~200 MB to ~30 MB with JLink, but API removals (JAXB, CORBA, sun.misc/Unsafe) and missing module versioning still block migration.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:43Introductions
- 3:35BJ Hargrave
- 8:08Multirelease jars
- 10:40Modularity in Java
- 14:15Kill Switch
- 16:40Versioning
- 18:50Multi Release Jars
- 22:55New Public API
- 23:51The real benefits of modularity
- 24:46The dark future of modularity
- 26:15Audience questions
- 27:17Hard sell
- 28:13Job 11 Docs
- 29:28Audience Question
- 30:47Small is key
related talks
51mJava Modularity: Life After Java 9
01h 02mJava 9 Modularity in Action
51mJava Modularity: the Year After
43mMonoliths to Modular: Navigating the Transition
46mModular Development with JDK 9 and Beyond
46mJDK 9, 10 and 11: Pitfalls For The Unwary
49m55 New Features in JDK 9
51mModular Development with JDK 9