Skip to content

Add migration guide and skill entry for javax to jakarta transition#1537

Merged
aaronpowell merged 2 commits intogithub:stagedfrom
thevinodkumar:staged
Apr 28, 2026
Merged

Add migration guide and skill entry for javax to jakarta transition#1537
aaronpowell merged 2 commits intogithub:stagedfrom
thevinodkumar:staged

Conversation

@thevinodkumar
Copy link
Copy Markdown
Contributor

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the staged branch for this pull request.

Description

Adds a new skill file for migrating Java projects from the javax.* namespace to the jakarta.* namespace, required when upgrading to Tomcat 11 / Jakarta EE 10+. The skill provides a step-by-step procedure covering: scanning for javax.* usages that require migration, identifying JDK-owned packages that must remain as javax.*, updating pom.xml dependency coordinates, updating web.xml namespace declarations, replacing imports in Java source files, and verifying the result with Maven commands.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • Update to existing instruction, prompt, agent, plugin, skill, or workflow.
  • Other (please specify):

Additional Notes

The skill is located at .github/skills/javax-to-jakarta-migration/SKILL.md. It is auto-loaded by GitHub Copilot when javax.* imports are detected or when the user asks about migrating to Jakarta EE 10 / Tomcat 11. The skill distinguishes between Jakarta EE packages that must be migrated (e.g. javax.servlet.*, javax.persistence.*) and JDK-owned packages that must stay as javax.* (e.g. javax.sql.*, javax.crypto.*, javax.naming.*), preventing accidental incorrect migrations.


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

This document provides a comprehensive guide for migrating Java code from the javax namespace to the jakarta namespace, including steps for scanning, updating dependencies, and verifying the migration.
@github-actions
Copy link
Copy Markdown
Contributor

🔍 Skill Validator Results

✅ All checks passed

Scope Checked
Skills 1
Agents 1
Total 2
Severity Count
--- ---:
❌ Errors 0
⚠️ Warnings 0
ℹ️ Advisories 0

Summary

Level Finding
ℹ️ Found 1 skill(s)
ℹ️ [javax-to-jakarta-migration] 📊 javax-to-jakarta-migration: 665 BPE tokens [chars/4: 626] (detailed ✓), 9 sections, 2 code blocks
ℹ️ ✅ All checks passed (1 skill(s))
Full validator output ```text Found 1 skill(s) [javax-to-jakarta-migration] 📊 javax-to-jakarta-migration: 665 BPE tokens [chars/4: 626] (detailed ✓), 9 sections, 2 code blocks ✅ All checks passed (1 skill(s)) ```

@thevinodkumar
Copy link
Copy Markdown
Contributor Author

@all-contributors add @thevinodkumar for Skills 🧰

@allcontributors
Copy link
Copy Markdown
Contributor

@thevinodkumar

I couldn't determine any contributions to add, did you specify any contributions?
Please make sure to use valid contribution names.

@aaronpowell aaronpowell merged commit daa7f3d into github:staged Apr 28, 2026
10 checks passed
fizznix pushed a commit to fizznix/awesome-copilot that referenced this pull request Apr 29, 2026
…ithub#1537)

* Add migration guide from javax to jakarta namespace

This document provides a comprehensive guide for migrating Java code from the javax namespace to the jakarta namespace, including steps for scanning, updating dependencies, and verifying the migration.

* Add javax to jakarta migration skill entry
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants