Agent skill · software engineering · 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.
Why this skill is useful
Provides specific commands and patterns for migrating Java code to the Jakarta namespace that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
javax → jakarta Migration Skill 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: Do NOT migrate these (they remain in javax.): javax.sql. — part of JDK javax.naming. — part of JDK (JNDI) javax.crypto. — part of JDK javax.net. — part of JDK javax.security.auth. — part of JDK javax.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) Step 4 — Update Java Source Files Replace all javax. imports with jakarta. equivalents in .java files. Step 5 — Verify 1. Run mvn clean compile or gradlew build — fix any compilation errors 2. Run mvn test or gradlew test — ensure all tests pass 3. 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/javax-to-jakarta-migration