The new Class-File API, presented by Brian Goetz at JVMLS, is a JDK-native API for reading, transforming, and generating Java bytecode. Currently, frameworks like Spring Boot and Hibernate rely on third-party bytecode libraries such as ASM, which must be updated every time the bytecode level changes with a new Java release. This creates a painful dependency chain where upgrading Java forces upgrading most of the dependency tree. Because the Class-File API is always in sync with the current bytecode level, frameworks that adopt it won't need to be updated just because the Java version changes. The API is expected to preview in 2024 and finalize around Java 25, with real ecosystem benefits arriving around Java 26 or 29 (2026–2027).
Table of contents
▚ Bytecode Basics▚ Bytecode Manipulation Basics▚ Migration Pains▚ Class-file API▚ Alleviating Migration Pains▚ Timeline▚ OutroSort: