agentleFS
MicrosoftKnown publishermicrosoft/MicroHack/03-Azure/01-01-App Innovation/03_GHCPAppModernization/templates/skills/java-upgrade/SKILL.md

java-upgrade

Skill220 starsChanged 7 days agoMITView on GitHub

Transformation rules and verification steps for upgrading Java 8/11 + Spring Boot 2.x applications to Java 25 + Spring Boot 4.x. WHEN: upgrade Java version, migrate Spring Boot 2 to 3, javax to jakarta, fix CVE in Java dependencies, update Maven/Gradle build for Java 25, Spring Security 5 to 6 migration, Spring Boot 3 to 4 migration. NOT for: greenfield Java services, framework replacement rewrites (Struts/EJB — use dedicated migration rulebooks), infrastructure-only changes.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Java 8 / Spring Boot 2.x → Java 25 / Spring Boot 4.x Upgrade Rules

Purpose

Packages the version-step strategy, API mappings, and verification checklist for a behavior-preserving upgrade to Java 25 + Spring Boot 4.x.

Prerequisites

  • ASSESSMENT.md exists and is approved.
  • Target JDK + compatible Maven installed — verify: java -version, mvn -version.

Procedure

Step 1 — Upgrade incrementally (never skip)

StepFrom → ToKey risk at this step
1Java 8 → 11Removed JEE modules (JAXB, JAX-WS) — add explicit deps
2Java 11 → 17Strong encapsulation of JDK internals (--add-opens smells)
3Java 17 → 21Mostly safe; check agents/bytecode libs (ASM, CGLIB versions)
4Java 21 → 25Recheck bytecode/agent libs and build-plugin versions for the new class-file level
5Boot 2.x → 2.7Deprecation cleanup before the big jump
6Boot 2.7 → 3.xjavax → jakarta, Spring Security 6, Hibernate 6
7Boot 3.x → 4.xAPIs deprecated in 3.x are removed — clean up all deprecation warnings first
mvn -q clean verify   # run after EVERY step; fix before proceeding

Step 2 — Apply transformation rules (Boot 2.7 → 3.x)

Source patternTarget patternNotes
javax.persistence.* / javax.servlet.* / javax.validation.*jakarta.*Also grep XML, persistence.xml, reflection strings
WebSecurityConfigurerAdapterSecurityFilterChain beanSpring Security 6 lambda DSL
antMatchers()requestMatchers()Security DSL rename
spring.factories (auto-config)AutoConfiguration.importsNew registration file
httpTrace / deprecated actuator IDsnew actuator endpoint IDsCheck management.endpoints config
Hibernate 5 dialects/typesHibernate 6 equivalentsID generation defaults changed — verify sequences
springfox (Swagger)springdoc-openapispringfox is incompatible with Boot 3
{{APP_SPECIFIC_RULE_1}}{{TARGET_1}}{{NOTE}}
{{APP_SPECIFIC_RULE_2}}{{TARGET_2}}{{NOTE}}

Step 3 — Verify

  • mvn clean verify passes on the target JDK (Java 25)
  • grep -r "javax\." src/ returns only intentional matches (e.g. javax.crypto, javax.sql stay in the JDK)
  • App starts; health endpoint returns UP
  • CVE assessment clean of criticals (appmod-cve-assessment)
  • No --add-opens workarounds left without a tracked issue

Common Pitfalls

  • ⚠️ javax. survivors outside Java code — XML configs, import strings in reflection, SPI files. The compiler won't save you; grep everything.
  • ⚠️ Hibernate 6 sequence allocation changes — verify generated IDs against existing DB sequences before deploying.
  • ⚠️ Lombok/annotation processors need versions matching the new JDK — upgrade build plugins (maven-compiler-plugin ≥ 3.11) first.
  • ⚠️ Trailing-slash matching changed in Spring 6 — /api/foo/ no longer matches /api/foo by default.
  • ⚠️ {{APP_SPECIFIC_PITFALL}}

References

  • Spring Boot 3.x and 4.x migration guides; Spring Security 6 migration guide
  • OpenRewrite recipes: org.openrewrite.java.spring.boot3.UpgradeSpringBoot_3_x
  • appmod assessment report (linked from ASSESSMENT.md)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.