Modular Development with JDK 9
summary
JDK 9 adds a module system that enforces strong encapsulation (public classes are hidden unless a package is exported) and reliable dependencies (requires graph, no split packages, no cyclic requires). Existing jars can become automatic modules on the module path, jdeps helps infer requires, and jlink builds custom runtime images. Example: GlassFish fails on JDK 9 when it accesses a non‑exported Sun class (illegal access). Some Java EE modules are deprecated and disabled by default.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:57Modular Development with JOK 9
- 10:23Reusing a Module
- 12:50The unit of reuse is the unit of release.
- 14:17Running a Modular Application
- 19:30Split packages in the real world
- 23:42Modular program structure
- 26:13Typical application
- 27:56Running the application
- 32:48Automatic modules
- 41:13Summary of Summaries
related talks
53mModular Development with JDK 9
46mModular Development with JDK 9 and Beyond
49mModular Development with JDK 9
47mJDK 9, 10, and 11: Pitfalls for the Unwary
01h 02mJava 9 Modularity in Action
46mJDK 9, 10 and 11: Pitfalls For The Unwary
23mWhat should I care about JDK 9 module system?
51mPrepare for JDK 9