Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment
GuideGuide

Java 8 upgrade: the paths to 17, 21 and 25.

Most of the work sits in the first step off Java 8. Here is what breaks, which tools automate the mechanical part, and how to decide between upgrading and rewriting.

AceMQ engineering team8 min readEngineer-reviewedUpdated

upgrade-path.mdLTS to LTS
Upgrade pathJava 8 → 25
What changes at each step
8 → 11Java EE modules and CORBA leave the JDKHigh
11 → 17JDK internals locked down, --illegal-access goneHigh
17 → 21Usually a smaller stepLow
21 → 25Newest LTS: check framework certificationLow
Severity is typical, not measured on your code

On this page

  • Java
  • Jakarta EE
  • Spring Boot
  • OpenRewrite
  • Tomcat
  • AWS Transform
  • GitHub Copilot
  • AWS
  • Spring
  • Oracle Database
  • Maven
  • Gradle
The short answer

A Java 8 upgrade has three paths: Java 17, 21 or 25, all long-term support releases. Pick the newest one your frameworks, application server and vendor agents certify; the code changes are largely the same for each, because the break happens when you leave Java 8. Recipes and AI-assisted tools handle the mechanical changes, and your tests decide whether the result is correct.

ServiceJava upgradeWhat breaks, what a recipe can fix, and what needs a person.See the service

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 21 · LTS since September 2023

Java 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.

What breaks on this path
Java 11Java EE modules and CORBA removed from the JDKHigh
Java 15Nashorn JavaScript engine removedMedium
Java 17JDK internals strongly encapsulated; --illegal-access removedHigh
Java 2117 to 21 is usually a smaller step: deprecated APIs still in useLow
Every stepBytecode tools, agents and build plugins need current versionsMedium
Framework versions to match
Spring Boot3.x needs Java 17 or later. Check your version’s docs for 21.
Jakarta EE9 or later with Spring Boot 3.
Tomcat10.1 implements Jakarta EE 10. Check its Java version page for 21.
Tool support
OpenRewriteMigration recipes for Java 21.
AWS TransformCheck AWS documentation for current targets.
CopilotCheck GitHub documentation for current targets.

02 · 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.

AreaWhat breaksUsual fix
Java EE modulesJAXB, JAX-WS, JAF and CORBA left the JDK in Java 11Add them back as Maven or Gradle dependencies
JDK internalsStrong encapsulation in Java 17: libraries that reflect into java.base fail at runtimeUpdate the library; use --add-opens only as a stopgap
Bytecode tools and agentsASM, Byte Buddy, Mockito, Lombok, JaCoCo and APM agents that predate the target class-file versionUpdate them first, before any code change
javax to jakartaOnly if you also move to Spring Boot 3 or Tomcat 10.1 or laterOpenRewrite recipe; see javax to Jakarta migration
Removed APIsNashorn (removed in Java 15) and the Security Manager (disabled from Java 24)Replace the engine or the control; no drop-in fix
Default charsetUTF-8 became the default in Java 18; code that relied on the platform charset reads files differentlySet the charset explicitly in file and stream code
Build and runtimeMaven or Gradle plugins, CI images, container base images and JVM flags that assume Java 8Edit 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.

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

A rough guide to scope, not a price
Effort positionQualitative
Typical
LighterTypicalHeavier
Pushing the scope up
Nothing at the top setting
PriceQuote on request
Get a fixed price in the assessment

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:

Your answers
Q1Still fits the business?Now
Q2Frameworks have a way forward?—
Q3Tests pin down behavior?—
Question 1 of 3Does the application still do what the business needs?If the process it supports has changed, upgrading the code preserves the wrong thing.
01

Upgrade if tests exist or can be written, the frameworks have a maintained successor and the code is understood by the team.

02

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.

03

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.

DistributionStandard support endsExtended or paid support endsSource
Oracle JDK 8March 2022 (Premier Support)December 2030 (Extended Support)Oracle Java SE Support Roadmap
Red Hat build of OpenJDK 830 Nov 2026 (full support)31 Dec 2032 (Extended Life Cycle Support)Red Hat OpenJDK life cycle
Amazon Corretto 831 Dec 2030None listedAmazon Corretto
Eclipse Temurin 8At least 31 Dec 2030None listedAdoptium support
Azul Zulu 831 Dec 203031 Dec 2032 (extended)Azul support roadmap
Microsoft Build of OpenJDKNo Java 8 build of its ownNot applicableMicrosoft OpenJDK support

07 · Next step

How does Ace8 run a Java 8 upgrade?

Ace8 is the modernization practice of AceMQ.

  1. 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.

  2. 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.

FAQ

Frequently asked questions

Short answers to what buyers ask first. Something else on your mind? Ask an engineer.

Yes. Java upgrades do not have to stop at each LTS. The work is the same changes you would make for 17, plus checking that your frameworks, server and agents certify 21. Test coverage matters more than the number of versions skipped.

Fixed-price assessment

Get a Java upgrade estimate. Per application, before any code changes.

The assessment lists every JDK vendor and version you run. It names the frameworks that pin you to Java 8 and proposes a target version per application. Price: quote on request; it changes with the number of applications and repositories.

Assess
JDK vendors, versions, blocking frameworks and a target per application.
Modernize
Recipes, AI-assisted tools and engineer review, application by application.
Run
AceMQ supports the upgraded stack 24/7 after go-live.

Get in touch

Talk to a modernization engineer.

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.