CAMEL-24188: Promote camel-jbang to stable

[davsclaus]

Summary

Claude Code on behalf of davsclaus

Promotes camel-jbang and TUI from Preview/Experimental to Stable support level. The MCP Server modules are also promoted to Stable.

Changes

• Changed supportLevel from Preview to Stable in 11 camel-jbang modules
• Changed supportLevel from Experimental to Stable in camel-jbang-plugin-tui
• Removed Preview status notices from camel-jbang-tui.adoc and camel-jbang-mcp.adoc
• Added upgrade guide entry documenting the promotion

Note: camel-jbang-plugin-edit intentionally remains at Preview.

Test plan

• Verify all 12 pom.xml files have <supportLevel>Stable</supportLevel>
• Verify camel-jbang-plugin-edit remains at Preview
• Build passes (metadata regeneration picks up new support level)

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[gnodet]

Review: CAMEL-24188 — Promote camel-jbang to Stable

Clean, consistent promotion. All 12 jbang modules are bumped to Stable, preview/experimental notices are removed from the docs, and the upgrade guide entry is in place.

One observation

camel-jbang-plugin-edit (firstVersion 4.12.0) still has <supportLevel>Preview</supportLevel> and is not included in this PR. It's been around longer than some of the modules being promoted (TUI at 4.20.0, MCP plugin at 4.21.0). Is this intentional or an oversight?

Everything else looks good

• All 11 Preview → Stable and 1 Experimental → Stable changes are consistent
• Doc removals in camel-jbang-mcp.adoc and camel-jbang-tui.adoc match the promotion
• Upgrade guide entry documents the promotion clearly

LGTM ✅

---

🤖 This review was generated by an AI agent (Claude Code) on behalf of gnodet. Opinions and technical assessments are AI-generated and should be validated by human reviewers.

[gnodet]

Re-review of commit 2 (1a1dad7) — regenerated file update

The 2nd commit regenerates jbang-console.json to sync the supportLevel field from "Preview" to "Stable", matching the promotion in commit 1. This is a single-line change in a generated file — exactly what's expected after modifying the support level metadata.

Approval stands.

---

Claude Code on behalf of gnodet — AI-generated review

[github-actions]

🧪 CI tested the following changed modules:

• docs
• dsl/camel-jbang/camel-jbang-console
• dsl/camel-jbang/camel-jbang-core
• dsl/camel-jbang/camel-jbang-main
• dsl/camel-jbang/camel-jbang-mcp
• dsl/camel-jbang/camel-jbang-plugin-generate
• dsl/camel-jbang/camel-jbang-plugin-kubernetes
• dsl/camel-jbang/camel-jbang-plugin-mcp
• dsl/camel-jbang/camel-jbang-plugin-route-parser
• dsl/camel-jbang/camel-jbang-plugin-test
• dsl/camel-jbang/camel-jbang-plugin-tui
• dsl/camel-jbang/camel-jbang-plugin-validate
• dsl/camel-jbang/camel-launcher

---

🔬 Scalpel shadow comparison — Scalpel: 14 tested, 3 compile-only — current: 7 all tested

Maveniverse Scalpel detected 17 affected modules (current approach: 7).

⚠️ Modules only in Scalpel (10)

• camel-jbang-core
• camel-jbang-it
• camel-jbang-main
• camel-jbang-plugin-edit
• camel-jbang-plugin-generate
• camel-jbang-plugin-kubernetes
• camel-jbang-plugin-test
• camel-launcher
• coverage
• docs

Skip-tests mode would test 14 modules (13 direct + 1 downstream), skip tests for 3 (generated code, meta-modules)

Modules Scalpel would test (14)

• camel-jbang-console
• camel-jbang-core
• camel-jbang-main
• camel-jbang-mcp
• camel-jbang-plugin-generate
• camel-jbang-plugin-kubernetes
• camel-jbang-plugin-mcp
• camel-jbang-plugin-route-parser
• camel-jbang-plugin-test
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-launcher
• camel-launcher-container
• docs

Modules with tests skipped (3)

• camel-jbang-it
• camel-jbang-plugin-edit
• coverage

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

⚠️ Some tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

• dsl/camel-jbang/camel-jbang-core: 1 test(s) disabled on GitHub Actions
• dsl/camel-jbang/camel-jbang-mcp: 1 test(s) disabled on GitHub Actions
• dsl/camel-jbang/camel-jbang-plugin-kubernetes: 8 test(s) disabled on GitHub Actions

💡 Manual integration tests recommended:

You modified dsl/camel-jbang/camel-jbang-core, dsl/camel-jbang/camel-jbang-main, dsl/camel-jbang/camel-jbang-plugin-generate, dsl/camel-jbang/camel-jbang-plugin-kubernetes, dsl/camel-jbang/camel-jbang-plugin-test, dsl/camel-jbang/camel-launcher. The related integration tests in dsl/camel-jbang/camel-jbang-it are excluded from CI. Consider running them manually:

mvn verify -f dsl/camel-jbang/camel-jbang-it -Djbang-it-test

All tested modules (17 modules)

• Camel :: Coverage
• Camel :: Docs
• Camel :: JBang :: Console
• Camel :: JBang :: Core
• Camel :: JBang :: Integration tests
• Camel :: JBang :: MCP
• Camel :: JBang :: Main
• Camel :: JBang :: Plugin :: Edit
• Camel :: JBang :: Plugin :: Generate
• Camel :: JBang :: Plugin :: Kubernetes
• Camel :: JBang :: Plugin :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Testing
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher
• Camel :: Launcher :: Container

---

⚙️ View full build and test results