菜单
Migrates Java EE 7/8 applications (WebLogic, JBoss, WildFly) to Quarkus 3. Use when moving off a traditional Java EE application server to the Quarkus runtime, not just renaming javax to jakarta.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Reads PLAN.md and executes each migration step sequentially. Applies transformations file by file, consulting domain-specific reference patterns provided by loaded migration skills. Use after the plan stage has produced PLAN.md.
Reads a project and a goal statement, then produces PLAN.md in the repo root. The plan is specific to THIS project — real file paths, real dependencies, real layer ordering. Uses graphify to generate a code graph, then selectively reads complex files. Does NOT execute any changes. Output is always PLAN.md and nothing else. Use when starting a new migration to create the migration plan before any code changes.
Runs the project build command, parses compiler errors, applies conservative fixes, and iterates until the build passes or max iterations are reached. Use after the execute stage has finished migrating source files.
Migrates EJB components to CDI managed beans.
Migrates Maven POM files from Java EE to Jakarta EE.
Enforces that no javax.* imports remain after migration.
| name | javaee-to-quarkus |
| description | Migrates Java EE 7/8 applications (WebLogic, JBoss, WildFly) to Quarkus 3. Use when moving off a traditional Java EE application server to the Quarkus runtime, not just renaming javax to jakarta. |
| license | Apache-2.0 |
| metadata | {"source":"java-ee-7","target":"quarkus-3","language":"java","build_tool":"maven: mvn compile","guide_url":"https://quarkus.io/guides/migration-guide","generated_by":"migration-skills-generator","generated_at":"2026-07-20T00:00:00.000Z"} |
Prerequisite: Ensure your application compiles on Java EE before starting. Java 17 is the minimum JDK for Quarkus 3.
This migration goes beyond a javax-to-jakarta namespace rename. It replaces the Java EE programming model with Quarkus: EJB → CDI managed beans, JMS/MDB → SmallRye Reactive Messaging, WAR → JAR packaging, persistence.xml → application.properties, JNDI lookups → direct injection, and app server lifecycle hooks → Quarkus lifecycle events. The result is a standalone Quarkus application with no application server dependency.
Execute in order. After each phase, run the project build and stop if it fails.
modules/build-config.md.modules/app-config.md.modules/ejb-to-cdi.md.modules/messaging.md.modules/lifecycle.md.modules/cleanup.md.Load each phase's module when starting that phase. Each module contains before/after code examples and references mapping tables in references/. Apply every applicable transformation to the codebase.
After completing each phase:
build_tool field above, or detect from project files: pom.xml → mvn compile)