davsclaus opened a new issue, #132:
URL: https://github.com/apache/camel-jbang-examples/issues/132
Since Citrus 5.0.0, the `jbang` group of the Camel test actions is
deprecated. Citrus describes it as "Connect with Camel JBang to run commands.
Deprecated, please use Camel CLI instead." The new name is `cli`. It takes the
same keys (`run`, `verify`, `stop`, ...): in Citrus, `setJbang` only calls
`setCli`.
All 42 Citrus tests in this repository still use `camel: jbang:` (127
lines). No test uses `camel: cli:` yet.
**Why it matters now**
- The Camel CLI bundles the Citrus tests of these examples as samples for AI
agents (`camel_catalog_examples` with filter `citrus`). Models copy what they
read, so they learn the deprecated form.
- The Camel AI tools are about to check a Citrus test against the test
schema of the Citrus catalog. Their hint for a log check already writes `camel:
cli:`, so the samples and the hint should agree.
**Proposal**
In every test, write `cli:` instead of `jbang:` under `camel:`:
```yaml
- camel:
cli: # was: jbang:
run:
integration:
name: "orders"
file: "../orders.camel.yaml"
```
Then run the tests (`camel test run`) to check that they still pass. Camel's
bundled copies follow with the next sync of the examples.
<details>
<summary>The 42 tests</summary>
- `ai/langchain4j-chat/test/langchain4j-chat.citrus.it.yaml`
- `ai/mcp-server/test/mcp-server.citrus.it.yaml`
- `ai/ticket-classifier/test/ticket-classifier.citrus.it.yaml`
- `cloud/aws-sqs/test/aws-sqs.citrus.it.yaml`
- `cloud/kubernetes-secrets/test/news-service.citrus.it.yaml`
- `cloud/kubernetes-service/test/news-service.citrus.it.yaml`
- `connect-service/artemis/test/artemis.citrus.it.yaml`
- `connect-service/camel-1-tribute/test/camel-1-tribute.citrus.it.yaml`
- `connect-service/ftp/test/ftp.citrus.it.yaml`
- `connect-service/jms-request-reply/test/jms-request-reply.citrus.it.yaml`
- `connect-service/kafka-orders/test/kafka-orders.citrus.it.yaml`
- `connect-service/mqtt/test/mqtt.citrus.it.yaml`
- `connect-service/sql/test/sql.citrus.it.yaml`
- `connect/file-processing/test/file-processing.citrus.it.yaml`
- `connect/http-client/test/http-client.citrus.it.yaml`
- `connect/stock-api/test/stock-api.citrus.it.yaml`
- `contracts/openapi-client/test/openapi-client.citrus.it.yaml`
- `contracts/openapi-server/test/openapi-server.citrus.it.yaml`
- `contracts/rest-code-first/test/rest-code-first.citrus.it.yaml`
- `fail-well/circuit-breaker/test/circuit-breaker.citrus.it.yaml`
- `fail-well/error-handling/test/error-handling.citrus.it.yaml`
- `quick-start/rest-api/test/rest-api.citrus.it.yaml`
- `quick-start/routes/test/routes.citrus.it.yaml`
- `quick-start/splitter/test/splitter.citrus.it.yaml`
- `quick-start/timer-log/test/timer-log.citrus.it.yaml`
- `route/aggregator/test/aggregator.citrus.it.yaml`
- `route/content-based-router/test/content-based-router.citrus.it.yaml`
- `route/dynamic-routing/test/dynamic-routing.citrus.it.yaml`
- `route/enrich-and-dedupe/test/enrich-and-dedupe.citrus.it.yaml`
- `route/filter-and-multicast/test/filter-and-multicast.citrus.it.yaml`
- `route/order-lines/test/order-lines.citrus.it.yaml`
- `run/nightly-report/test/nightly-report.citrus.it.yaml`
- `run/order-generator/test/order-generator.citrus.it.yaml`
- `run/properties-and-profiles/test/properties-and-profiles.citrus.it.yaml`
-
`showcase/smart-log-analyzer/first-iteration/test/first-iteration.citrus.it.yaml`
- `transform/csv-to-json/test/csv-to-json.citrus.it.yaml`
- `transform/data-mapping/test/data-mapping.citrus.it.yaml`
- `transform/groovy/test/groovy.citrus.it.yaml`
- `transform/json-transform/test/json-transform.citrus.it.yaml`
- `transform/xml-to-json/test/xml-to-json.citrus.it.yaml`
- `transform/xslt/test/xslt.citrus.it.yaml`
- `transformation/edi-x12-as2/test/edi-x12-as2.citrus.it.yaml`
</details>
_Claude Code on behalf of davsclaus_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
