Prepare for JDK 9
summary
JDK 9 modularizes the platform, deprecates six SE modules (activation, jaxb, jax‑ws, transaction, corba, xmlws annotation) and stops resolving them by default so code that previously compiled may fail unless those APIs are added back with add-modules or replaced by standalone jars from Maven Central. Runtime prints a one‑time illegal reflective access warning and offers --illegal-access=deny to test future failures. Use --release for cross‑compiles, run jdeps to find internal API use, and upgrade tools (builds, IDEs, agents) before migrating.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:16General compatibility policies
- 2:53The good news
- 13:22Migration options
- 16:22javac symbol database (JDK 6. JDK 8)
- 23:07Illegal reflective access warning
- 24:42New version-string scheme, JEP 223
- 27:49New binary structure for JRE and JDK JEP 220
- 33:21Multi-release JAR files - JEP 238
- 37:26Compiling to older releases
- 39:36What can I do to prepare for JDK 9
related talks
47mJDK 9, 10, and 11: Pitfalls for the Unwary
51mPrepare for JDK 9
49mPreparing for JDK 9 - AKA The Sharp Edges of JDK 9
46mJDK 9, 10 and 11: Pitfalls For The Unwary
49mModular Development with JDK 9
46mModular Development with JDK 9 and Beyond
53mModular Development with JDK 9
50mJDK 11: Pitfalls for the Unwary
