The Do's and Don'ts with Java 9
summary
Module descriptors can break the Maven ecosystem by changing jar identity: adding a module name is final and can make previously coexisting versions collide, and about 30,000 group/artifact combinations exhibit risky naming patterns. Maven 3.5 shows colored warnings for falling back to Automatic-Module-Name (derived from the JAR filename); libraries should add Automatic-Module-Name in the manifest with a carefully chosen reverse‑DNS module name, avoid split packages, keep Maven folder layout, use javac --release or animal-sniffer, and understand module path vs class path constraints.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:52MODULENAMES WITH NUMBERS
- 5:42AUTOMATIC MODULE NAMES
- 9:52AUTOMATIC MODULES
- 10:56CONFERENCE EXAMPLE
- 17:34MISTAKES WILL HAPPEN
- 18:30TIPS FOR USING JAVA 9 WITH MAVEN
- 21:18CAN EVERY PROJECT BECOME MODULAR?
- 22:15THE BOOMERANG QUESTION
- 23:56POM HYGIENE
- 25:26OTHER QUESTIONS?
related talks
49mTo JAR Hell And Back - A Live Migration to the Java 9 Module System
54mBeginning Java 9 Modules
48mThe Java Module System in practice
50mJDK 11: Pitfalls for the Unwary
49mModular Development with JDK 9
46mJDK 9, 10 and 11: Pitfalls For The Unwary
23mWhat should I care about JDK 9 module system?
53mModular Development with JDK 9