01 · Paths
Should you upgrade Java 8 to 17, 21 or 25?
Upgrade to the newest LTS that your frameworks and vendors certify, which is Java 21 or 25 in most estates and Java 17 when a vendor product stops there. The migration work is largely the same for each target, so a later target buys a longer window for the same effort.
Java 8 to 17
Java 17 is the smallest jump and the minimum for Spring Boot 3 and Spring Framework 6. The smallest jump that reaches Spring Boot 3. Choose it when a vendor product you depend on is certified only to 17.
--illegal-access removedHighJava 8 to 21
Java 21 is the widely certified middle option and adds virtual threads. The usual target: the same migration work as 17, with a later LTS. Choose it when your frameworks and vendors certify 21.
--illegal-access removedHighJava 8 to 25
Java 25 is the newest LTS. Check every agent, plugin and application server against it before you commit.
--illegal-access removedHigh02 · What breaks
What breaks when you move off Java 8?
Java 8 vs 17 vs 21 lists what changes at each step, and the Java upgrade service describes how Ace8 delivers it.
| Area | What breaks | Usual fix |
|---|---|---|
| Java EE modules | JAXB, JAX-WS, JAF and CORBA left the JDK in Java 11 | Add them back as Maven or Gradle dependencies |
| JDK internals | Strong encapsulation in Java 17: libraries that reflect into java.base fail at runtime | Update the library; use --add-opens only as a stopgap |
| Bytecode tools and agents | ASM, Byte Buddy, Mockito, Lombok, JaCoCo and APM agents that predate the target class-file version | Update them first, before any code change |
| javax to jakarta | Only if you also move to Spring Boot 3 or Tomcat 10.1 or later | OpenRewrite recipe; see javax to Jakarta migration |
| Removed APIs | Nashorn (removed in Java 15) and the Security Manager (disabled from Java 24) | Replace the engine or the control; no drop-in fix |
| Default charset | UTF-8 became the default in Java 18; code that relied on the platform charset reads files differently | Set the charset explicitly in file and stream code |
| Build and runtime | Maven or Gradle plugins, CI images, container base images and JVM flags that assume Java 8 | Edit each one; recipes do not touch them |
03 · Tools
Which tools automate a Java 8 upgrade?
OpenRewrite, AWS Transform and GitHub Copilot app modernization each automate part of it. They speed the first pass; none of them proves the result is correct, so every change still runs against your tests.
OpenRewrite
Deterministic recipes for Java version steps, Spring Boot 3 and jakarta. Same diff on every run, easy to review across many repositories.
AWS Transform
An AWS service that uses AI to automate code modernization tasks, including Java version upgrades, and reports what it changed.
GitHub Copilot app modernization
An IDE agent that assesses a Java application, plans the upgrade and applies changes with build and test steps.
04 · Effort
What drives the effort of a Java 8 upgrade?
Effort is driven by the state of each application, not by the size of the estate alone. These are the factors that move it most:
Test coverage
Without tests, nobody can say the upgraded application behaves the same.Dependency age
Libraries with no release for the target Java set the schedule.Framework version
Spring Boot 2 to 3 adds the jakarta rename on top of the Java change.Application server
Check your server's certification for the target Java, or plan a move to Tomcat or Spring Boot.Agents and bytecode tooling in the build and at runtime
Number of distinct JDK vendors and container images in the estate
05 · Decision
Should you upgrade or rewrite a Java 8 application?
Upgrade when the application's design still fits the business and rewrite when the design is the problem, not the runtime. A rule to apply per application:
Upgrade if tests exist or can be written, the frameworks have a maintained successor and the code is understood by the team.
Rewrite if the framework has no successor, nobody knows the behaviour and there are no tests, or the architecture blocks changes you need regardless of Java version.
In between, upgrade first to get current Java and Spring, then refactor the parts that hurt. See rehost, replatform, refactor or rewrite.
06 · Reference
Support dates by vendor
Dates checked 17 Nov 2026. Oracle and Red Hat dates were read on their own pages; the others come from endoflife.date, which links each vendor's page. Vendors extend dates, so confirm with yours.
Need to stay on Java 8 for now? OSSeva covers that.
| Distribution | Standard support ends | Extended or paid support ends | Source |
|---|---|---|---|
| Oracle JDK 8 | March 2022 (Premier Support) | December 2030 (Extended Support) | Oracle Java SE Support Roadmap |
| Red Hat build of OpenJDK 8 | 30 Nov 2026 (full support) | 31 Dec 2032 (Extended Life Cycle Support) | Red Hat OpenJDK life cycle |
| Amazon Corretto 8 | 31 Dec 2030 | None listed | Amazon Corretto |
| Eclipse Temurin 8 | At least 31 Dec 2030 | None listed | Adoptium support |
| Azul Zulu 8 | 31 Dec 2030 | 31 Dec 2032 (extended) | Azul support roadmap |
| Microsoft Build of OpenJDK | No Java 8 build of its own | Not applicable | Microsoft OpenJDK support |
07 · Next step
How does Ace8 run a Java 8 upgrade?
Ace8 is the modernization practice of AceMQ.
- 01
AceMQ engineers run OpenRewrite recipes first, use AI-assisted tools on what the recipes miss, and review every change against your tests. AceMQ supports the upgraded stack after go-live.
- 02
Get a Java upgrade estimate through the modernization assessment. It lists every JDK vendor and version you run, the frameworks that pin you to Java 8 and a target per application. If Tomcat is part of the estate, see the Tomcat 9 upgrade guide.