Upgrade Java applications to a newer JDK
An agent updates build files, dependencies and deprecated APIs to move an app to a newer Java version, then builds and tests it.
The use case
Many companies still run services on Java 8 or 11 because upgrades are tedious: dependency bumps, removed APIs, build plugin changes. Amazon Q Developer's transformation feature and GitHub Copilot's modernization tooling for Java plan the upgrade, edit the build files and source, build and run tests, and iterate on failures. The output is a set of changes plus a summary of what was done and what still needs work. Developers still review the diff, run integration and performance tests, and roll out the upgraded service gradually rather than all at once.
Example workflow
- Choose a service with a working build and tests
- Run the upgrade agent on a branch
- Review the change summary and dependency bumps
- Run integration and performance tests
- Roll out gradually with a rollback plan
Tools
- Amazon Q Developer
- GitHub Copilot
- Maven
- Gradle
Risks and guardrails
- Thin test suites let runtime breaks through
- Dependency bumps can change behavior or licenses
- Never deploy the result straight to production
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- AWS docs: upgrading Java with Amazon Q Developer: docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/code-transformation.html
- Microsoft Learn: GitHub Copilot modernization for Java: learn.microsoft.com/en-us/azure/developer/java/migration/migrate-github-copilot-app-modernization-for-java
- Amazon Q Developer (official page): aws.amazon.com/q/developer (checked 2026-11-19)