You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "davsclaus (via GitHub)" <gi...@apache.org> on 2026/09/13 17:15:41 UTC
[PR] CAMEL-24693: camel-jbang - camel_catalog_sample returns validated YAML samples of an EIP or file entry, from the catalog's documentation for the Camel version in use [camel]
davsclaus opened a new pull request, #26377:
URL: https://github.com/apache/camel/pull/26377
A new shared authoring tool, `camel_catalog_sample`: validated YAML samples of an EIP or a file entry (`onException`, `aggregate`, `circuitBreaker`, `split`, `rest`, `beans`, `routeConfiguration`, ...) by name, kebab-case, a part name (`onFallback`, `when`) or what to do ("read file", "call service", "batch", "retry", "router"), with where it goes: a top-level entry next to `route`, or a step inside `steps`.
The samples come from the catalog's own documentation for the Camel version in use (`camel_catalog_doc` style lookup of the `<name>-eip` page, every `[source,yaml]` block validated at lookup), so they are version-accurate; a shipped set (`eip-samples.json`, extracted from the docs and validated) is the fallback for the user-manual pages the catalog does not bundle. A `beans` entry has samples (a model that had just been told "beans is a list" asked for it and got nothing).
Why: in the benchmark a local model nested `onException` inside a route, was refused by the schema, looked the EIP up in the catalog, and learned every option and nothing about where it goes; it gave up after seven minutes. With this tool that step became three calls. The same question ("what does a correct one look like") is what a person asks the docs.
Tests: `CatalogSamplesTest` (9), `AuthoringToolsTest` (core and mcp). 6 files, most of the lines the JSON.
Follow-ups noted on CAMEL-24693: the shipped set generated by a mojo in camel-jbang-core's build; the EIP pages are guarded by #26375.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] CAMEL-24693: camel-jbang - camel_catalog_sample returns validated YAML samples of an EIP or file entry, from the catalog's documentation for the Camel version in use [camel]
Posted by "davsclaus (via GitHub)" <gi...@apache.org>.
davsclaus merged PR #26377:
URL: https://github.com/apache/camel/pull/26377
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] CAMEL-24693: camel-jbang - camel_catalog_sample returns validated YAML samples of an EIP or file entry, from the catalog's documentation for the Camel version in use [camel]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #26377:
URL: https://github.com/apache/camel/pull/26377#issuecomment-5654921652
<!-- ci-tested-modules -->
:test_tube: **CI tested the following changed modules:**
- `dsl/camel-jbang/camel-jbang-core`
- `dsl/camel-jbang/camel-jbang-mcp`
---
<details><summary>:microscope: Scalpel shadow comparison — Scalpel: 7 tested, 8 compile-only — current: 6 all tested</summary>
[Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **15 affected modules** (current approach: 6).
<details><summary>:warning: Modules only in Scalpel (9)</summary>
- `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`
</details>
**Skip-tests mode would test 7 modules** (2 direct + 5 downstream), **skip tests for 8** (generated code, meta-modules)
<details><summary>Modules Scalpel would test (7)</summary>
- `camel-jbang-core`
- `camel-jbang-mcp`
- `camel-jbang-plugin-mcp`
- `camel-jbang-plugin-route-parser`
- `camel-jbang-plugin-tui`
- `camel-jbang-plugin-validate`
- `camel-launcher-container`
</details>
<details><summary>Modules with tests skipped (8)</summary>
- `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`
</details>
> :information_source: Shadow mode — Scalpel observes but does not affect test execution. [Learn more](https://github.com/maveniverse/scalpel)
</details>
:warning: **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
:bulb: **Manual integration tests recommended:**
> You modified `dsl/camel-jbang/camel-jbang-core`. 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
> ```
<details><summary>All tested modules (15 modules, 56.8s total)</summary>
**Total reactor time:** 56.8s
| Module | Duration | Status |
| --- | --- | --- |
| Camel :: JBang :: Plugin :: TUI | 28.0s | FAILURE |
| Camel :: JBang :: Plugin :: Kubernetes | 12.3s | SUCCESS |
| Camel :: JBang :: Plugin :: Testing | 7.4s | SUCCESS |
| Camel :: Coverage | 3.7s | SUCCESS |
| Camel :: JBang :: Plugin :: Validate | 1.3s | SUCCESS |
| Camel :: JBang :: Plugin :: Edit | 1.1s | SUCCESS |
| Camel :: JBang :: Plugin :: Generate | 1.0s | SUCCESS |
| Camel :: JBang :: Plugin :: Route Parser | 0.7s | SUCCESS |
| Camel :: JBang :: Main | 0.7s | SUCCESS |
| Camel :: JBang :: Plugin :: MCP | 0.6s | SUCCESS |
| Camel :: JBang :: Core | n/a | |
| Camel :: JBang :: Integration tests | n/a | |
| Camel :: JBang :: MCP | n/a | |
| Camel :: Launcher | n/a | |
| Camel :: Launcher :: Container | n/a | |
**Top 20 slowest modules:**
- `Camel :: JBang :: Plugin :: TUI` (28.0s)
- `Camel :: JBang :: Plugin :: Kubernetes` (12.3s)
- `Camel :: JBang :: Plugin :: Testing` (7.4s)
- `Camel :: Coverage` (3.7s)
- `Camel :: JBang :: Plugin :: Validate` (1.3s)
- `Camel :: JBang :: Plugin :: Edit` (1.1s)
- `Camel :: JBang :: Plugin :: Generate` (1.0s)
- `Camel :: JBang :: Plugin :: Route Parser` (0.7s)
- `Camel :: JBang :: Main` (0.7s)
- `Camel :: JBang :: Plugin :: MCP` (0.6s)
</details>
---
:gear: [View full build and test results](https://github.com/apache/camel/actions/runs/34771053220)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] CAMEL-24693: camel-jbang - camel_catalog_sample returns validated YAML samples of an EIP or file entry, from the catalog's documentation for the Camel version in use [camel]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #26377:
URL: https://github.com/apache/camel/pull/26377#issuecomment-5654804909
:star2: Thank you for your contribution to the Apache Camel project! :star2:
:robot: CI automation will test this PR automatically.
:camel: 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](https://camel.apache.org/community/team/#committers) have access to the summary.
:warning: Be careful when sharing logs. Review their contents before sharing them publicly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org