JDKs and SDKs
summary
Explains concrete mismatch failures and fixes: JDKs ship every ~6 months with LTS (8,11,17,21), the TCK is ~100,000 tests, and class file versions matter (for example class file 61 = Java 17, 52 = Java 8), so running SDK tools on the wrong JDK yields cryptic errors. Shows using JDK 20 + --release to check source target and APIs prevents runtime NoSuchMethod errors, outlines Gradle/Kotlin daemon version traps, SDK manager channels, emulator one-version limit, and toolchain/FuJ remedies.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker
- 1:04Audience and talk purpose
- 3:09What is a JDK
- 8:51Managing multiple JDKs
- 11:41Compiling and running across JDKs
- 16:20JDKs in Android builds
- 21:18Kotlin SDK and versions
- 24:09What is the Android SDK
- 30:47Compile, min, and target SDKs
- 35:24JDK and Android API levels
- 39:11Troubleshooting JDK errors
- 41:00Summary and closing
related talks
47mJDK 9, 10, and 11: Pitfalls for the Unwary
27mModern Java: Change is the Only Constant
22mMigrate early, migrate often! JDK release cadence strategies
49mJDK LTS Release Use Cases: When is a Java migration advisable?
49mJDK 8 to 25 Without the Pain - Engineering a Modern Java Platform
53mApproaching the JDK 25 LTS release through real-world migration
44mThe Future of Java SE
01h 01mJDK 17 - The New LTS Release Arrived in the Jungle