javax → jakarta Migration Skill
SkillDev toolsLets your agent rewrite Java imports from javax to jakarta to prepare code for Jakarta EE 10 or Tomcat 11.
Use javax → jakarta Migration Skill in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add javax → jakarta Migration Skill and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the javax → jakarta Migration Skill skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
About this skill
Migrate Java code from javax.* to jakarta.* namespace. Use when upgrading to Tomcat 11, Jakarta EE 10, or when javax imports are detected in the codebase.
What this skill tells your AI
The instructions your AI receives, as published by github/awesome-copilot in skills/javax-to-jakarta-migration/SKILL.md and read by ahel’s review.
When to Use
- Upgrading to Tomcat 11 / Jakarta EE 10+
- Code review detects
javax.*imports - Migrating an existing project to the jakarta namespace
Procedure
Step 1 — Scan for javax Usage
Search the codebase for all javax.* imports that need migration:
javax.servlet.* → jakarta.servlet.*
javax.persistence.* → jakarta.persistence.*
javax.validation.* → jakarta.validation.*
javax.annotation.* → jakarta.annotation.*
javax.inject.* → jakarta.inject.*
javax.enterprise.* → jakarta.enterprise.*
javax.faces.* → jakarta.faces.*
javax.ws.rs.* → jakarta.ws.rs.*
javax.el.* → jakarta.el.*
javax.json.* → jakarta.json.*
javax.mail.* → jakarta.mail.*
javax.websocket.* → jakarta.websocket.*
Do NOT migrate these (they remain in javax.*):
javax.sql.*— part of JDKjavax.naming.*— part of JDK (JNDI)javax.crypto.*— part of JDKjavax.net.*— part of JDKjavax.security.auth.*— part of JDKjavax.swing.*,javax.xml.parsers.*— JDK packages
Step 2 — Update pom.xml
Replace dependency coordinates:
| Old | New |
|---|---|
javax.servlet:javax.servlet-api | jakarta.servlet:jakarta.servlet-api:6.0.0 |
javax.persistence:javax.persistence-api | jakarta.persistence:jakarta.persistence-api:3.1.0 |
javax.validation:validation-api | jakarta.validation:jakarta.validation-api:3.0.2 |
javax.annotation:javax.annotation-api | jakarta.annotation:jakarta.annotation-api:2.1.1 |
Step 3 — Update web.xml (if present)
<!-- Old namespace -->
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" version="4.0">
<!-- New namespace -->
<web-app xmlns="https://jakarta.ee/xml/ns/jakartaee" version="6.0">
Step 4 — Update Java Source Files
Replace all javax. imports with jakarta. equivalents in .java files.
Step 5 — Verify
- Run
mvn clean compileorgradlew build— fix any compilation errors - Run
mvn testorgradlew test— ensure all tests pass - Search for any remaining
javax.*imports (excluding JDK packages)
Output
Provide a migration summary listing all files changed, imports replaced, and any manual steps required.
Signals
- GitHub stars
- 40k
- Forks
- 5k
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
javax-to-jakarta-migration- Source
- github.com/github/awesome-copilot
github.com/github/awesome-copilot