Upgrading Spring Boot applications from 2.x to the latest 3.x releases introduces significant changes across the framework, dependencies, and Jakarta namespace. These updates improve long-term support, performance, and compatibility with modern Java platforms, but the migration can surface breaking API changes and dependency mismatches. GitHub Copilot app modernization helps streamline this transition by analyzing your project, generating an upgrade plan, and applying targeted updates.
Supported Upgrade Path
GitHub Copilot app modernization supports upgrading Spring Boot applications to Spring Boot 3.5, including:
- Updating Spring Framework libraries to 6.x
- Migrating from javax to jakarta
- Aligning dependency versions with Boot 3.x
- Updating plugins and starter configurations
- Adjusting build files for the required JDK level
- Validating dependency updates and surfacing CVE issues
These capabilities complement the Microsoft Learn quickstart for upgrading Java projects using GitHub Copilot app modernization.
How GitHub Copilot app modernization helps
When you open a Spring Boot 2.x project in Visual Studio Code or IntelliJ IDEA and initiate an upgrade, GitHub Copilot app modernization performs:
Project Analysis
- Detects your current Spring Boot version
- Identifies incompatible starters, libraries, and plugins
- Flags javax.* imports requiring Jakarta migration
- Evaluates your build configuration and JDK requirements
Upgrade Plan Generation
The tool produces an actionable plan that outlines:
- New Spring Boot parent version
- Updated Spring Framework and related modules
- Required namespace changes from javax.* to jakarta.*
- Build plugin updates
- JDK configuration alignment for Boot 3
You can review and adjust the plan before applying changes.
Automated Transformations
GitHub Copilot app modernization applies targeted changes such as:
- Updating spring-boot-starter-parent to 3.5.x
- Migrating imports to jakarta.*
- Updating dependencies and BOM versions
- Rewriting removed or deprecated APIs
- Aligning test dependencies (e.g., JUnit 5)
Build / Fix Iteration
The agent automatically:
- Builds the project
- Captures failures
- Suggests fixes
- Applies updates
- Rebuilds until the project compiles successfully
This loop continues until all actionable issues are addressed.
Security & Behavior Checks
As part of the upgrade, the tool can:
- Validate CVEs introduced by dependency version changes
- Surface potential behavior changes
- Recommend optional fixes
Expected Output
After running the upgrade for a Spring Boot 2.x project, you should expect:
- An updated Spring Boot parent in Maven or Gradle
- Spring Framework 6.x and Jakarta-aligned modules
- Updated starter dependencies and plugin versions
- Rewritten imports from javax.* to jakarta.*
- Updated testing stack
- A summary file detailing:
- Versions updated
- Code edits applied
- Dependencies changed
- CVE results
- Remaining manual review items
Developer Responsibilities
GitHub Copilot app modernization accelerates technical migration tasks, but final validation still requires developer review, including:
- Running the full test suite
- Reviewing custom filters, security configuration, and web components
- Re-validating integration points
- Confirming application behavior across runtime environments
The tool handles mechanical upgrade work so you can focus on correctness, quality, and functional validation.
Learn more
For setup, prerequisites, and the broader Java upgrade workflow, refer to the official Microsoft Learn guide:
Quickstart: Upgrade a Java Project with GitHub Copilot App Modernization
Install GitHub Copilot app modernization for VS Code and IntelliJ IDEA
Microsoft