Migrating Beyond Java 8
summary
Migration from Java 8 to Java 11 commonly fails with concrete errors like java.lang.NoClassDefFoundError for JAXB and broken internal API calls; a demo app shows base64 encoder calls must switch to Base64.getEncoder()/getDecoder(), then adding the Jakarta/JAXB Maven/Gradle dependency fixes XML marshalling, and Open Liberty can supply Java EE libs for you. Use the Binary Scanner to list missing classes and removed APIs, run jdeps against your target JDK, update Gradle/Maven and libraries, enable automated checks like Dependabot and run full tests.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:05Common Questions
- 5:04Why migrate
- 8:18What are you migrating to
- 12:33Missing Libraries
- 15:48Removed APIs
- 19:43Outofdate dependencies
- 22:03Automation tools
- 25:48Tools
- 30:22Running on Java 8
- 34:19Running on Java 11
- 36:31Troubleshooting
- 38:55Gradle
- 42:03Next Steps
- 45:19GitHub
- 46:16Questions
- 53:49Hotspot or Open JDK
related talks
29mFarewell to Java 8
50mJava. Migrating to 11 in real app
43mEngineering a Modern Java Platform
49mJDK 8 to 25 Without the Pain - Engineering a Modern Java Platform
50mJDK 11: Pitfalls for the Unwary
47mJava. Migrating to 11 in real app
49mTo JAR Hell And Back - A Live Migration to the Java 9 Module System
48mTo JAR Hell And Back - A Live Migration to the Java 9