github/javax-to-jakarta-migration
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.
npx skills add https://github.com/github/awesome-copilot --skill javax-to-jakarta-migration
javax.* importsSearch 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 packagesReplace 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 |
<!-- 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">
Replace all javax. imports with jakarta. equivalents in .java files.
mvn clean compile or gradlew build — fix any compilation errorsmvn test or gradlew test — ensure all tests passjavax.* imports (excluding JDK packages)Provide a migration summary listing all files changed, imports replaced, and any manual steps required.
Take github/javax-to-jakarta-migration from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.