Farewell to Java 8
summary
A project migrates its codebase from Java 8 toward Java 11 but encounters broken Gradle/Maven plugins, failing tests, missing library artifacts, and an SSL/TLS negotiation bug that forces a temporary rollback to Java 10. The team avoids full JDK modularization and instead creates a jlink runtime image to keep binaries small and reproducible, runs full regression and manual tests, and performs code rewrites (FTP client, test plugins, Groovy/Spock) while watching for automatic-module issues, dependency churn, and large Docker image reductions (about 300MB → ~47MB).
AI-written summary · about
chapters (6)
- 0:00Introduction
- 7:13Why leave Java 8
- 10:23Migration challenges
- 18:08Skip module creation
- 23:11Java 11 Docker issues
- 26:05Four key lessons
related talks
50mJava. Migrating to 11 in real app
49mTo JAR Hell And Back - A Live Migration to the Java 9 Module System
56mMigrating Beyond Java 8
46mGoing Java::Current in Production
51mLife Beyond Java 8
46mJDK 9, 10 and 11: Pitfalls For The Unwary
50mJDK 11: Pitfalls for the Unwary
43mEngineering a Modern Java Platform