Run any Skill in Manus with one click

Get Started

upgrade

Stars0

Forks0

UpdatedApril 8, 2026 at 03:08

Upgrade Java runtime versions, frameworks, and dependencies to their latest compatible releases

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

brunoborges

brunoborges/gh-appmod

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	upgrade
description	Upgrade Java runtime versions, frameworks, and dependencies to their latest compatible releases

Upgrade

Upgrade Java runtime versions, frameworks, and dependencies.

Version-Specific Upgrade Guides

For detailed, JEP-by-JEP upgrade instructions, see the version-specific skills:

Java 8 → 11 — Module system, removed Java EE modules, var, HTTP Client
Java 11 → 17 — Records, Sealed Classes, Pattern Matching, Text Blocks
Java 17 → 21 — Virtual Threads, Pattern Matching for switch, Record Patterns
Java 21 → 25 — Flexible Constructors, Stream Gatherers, Class-File API

Steps

Analyze first — Scan the project structure, build files (pom.xml, build.gradle), and source code to determine current Java version, framework versions, and dependency versions.
Generate an upgrade plan — Produce a plan detailing what will be upgraded and what breaking changes to expect. Present the plan for review.
Apply changes incrementally — Make changes in logical groups:
- Build configuration (Java version, plugin versions)
- Dependencies (framework BOMs, library versions)
- Source code (API changes, deprecated method replacements)
- Configuration files (property renames, format changes)
Validate after each group — Run the build (mvn clean compile or gradle build) to confirm changes compile successfully. Run tests if available.
Check for vulnerabilities — After upgrading, scan for known vulnerabilities in the updated dependencies.

Guidelines

Prefer incremental upgrades over large version jumps when the gap is significant.
Always explain what changes are being made and why.
If a build fails after changes, analyze the error and attempt to fix it before reporting.
When multiple upgrade paths exist, present options and let the developer decide.

More from this repository

same repository

assess

brunoborges/gh-appmod

Assess a Java project's modernization posture — Java version, framework versions, dependency health, vulnerabilities, and migration opportunities

2026-04-080

deploy

brunoborges/gh-appmod

Deploy Java applications to Azure services including App Service, Container Apps, AKS, and Spring Apps

2026-04-080

java-11-to-17

brunoborges/gh-appmod

Upgrade Java projects from JDK 11 to JDK 17 covering Records, Sealed Classes, Pattern Matching for instanceof, Switch Expressions, Text Blocks

2026-04-080

java-17-to-21

brunoborges/gh-appmod

Upgrade Java projects from JDK 17 to JDK 21 covering Virtual Threads, Pattern Matching for switch, Record Patterns, Sequenced Collections

2026-04-080

java-21-to-25

brunoborges/gh-appmod

Upgrade Java projects from JDK 21 to JDK 25 covering Flexible Constructor Bodies, Stream Gatherers, Class-File API, Scoped Values, Security Manager removal

2026-04-080

java-8-to-11

brunoborges/gh-appmod

Upgrade Java projects from JDK 8 to JDK 11 covering module system, removed Java EE modules (JAXB, JAX-WS, CORBA), var keyword, HTTP Client, collection factory methods

2026-04-080

name	upgrade
description	Upgrade Java runtime versions, frameworks, and dependencies to their latest compatible releases

Upgrade

Upgrade Java runtime versions, frameworks, and dependencies.

Version-Specific Upgrade Guides

For detailed, JEP-by-JEP upgrade instructions, see the version-specific skills:

Java 8 → 11 — Module system, removed Java EE modules, var, HTTP Client
Java 11 → 17 — Records, Sealed Classes, Pattern Matching, Text Blocks
Java 17 → 21 — Virtual Threads, Pattern Matching for switch, Record Patterns
Java 21 → 25 — Flexible Constructors, Stream Gatherers, Class-File API

Steps

Analyze first — Scan the project structure, build files (pom.xml, build.gradle), and source code to determine current Java version, framework versions, and dependency versions.
Generate an upgrade plan — Produce a plan detailing what will be upgraded and what breaking changes to expect. Present the plan for review.
Apply changes incrementally — Make changes in logical groups:
- Build configuration (Java version, plugin versions)
- Dependencies (framework BOMs, library versions)
- Source code (API changes, deprecated method replacements)
- Configuration files (property renames, format changes)
Validate after each group — Run the build (mvn clean compile or gradle build) to confirm changes compile successfully. Run tests if available.
Check for vulnerabilities — After upgrading, scan for known vulnerabilities in the updated dependencies.

Guidelines

Prefer incremental upgrades over large version jumps when the gap is significant.
Always explain what changes are being made and why.
If a build fails after changes, analyze the error and attempt to fix it before reporting.
When multiple upgrade paths exist, present options and let the developer decide.