[
https://issues.apache.org/jira/browse/CAMEL-25261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-25261.
---------------------------------
Resolution: Fixed
> camel-jbang - bundle the examples of the ladder that run offline
> ----------------------------------------------------------------
>
> Key: CAMEL-25261
> URL: https://issues.apache.org/jira/browse/CAMEL-25261
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.23.0
>
>
> Only the quick-start examples (plus circuit-breaker and three showcase ones)
> are bundled with the Camel CLI; the rest of the ladder is downloaded from
> GitHub when run. Nineteen more examples need no Docker, no API key and no
> network:
> * run: order-generator, nightly-report, properties-and-profiles
> * transform: json-transform, xml-to-json, csv-to-json, data-mapping, groovy,
> xslt
> * route: content-based-router, order-lines, aggregator, filter-and-multicast
> * fail-well: error-handling
> * connect: file-processing, stock-api, http-client
> * contracts: openapi-server, openapi-client
> Bundling them (about 115 KB) makes the ladder work offline from quick-start
> to contracts, for {{camel run --example}}, the TUI example browser, and the
> MCP tools. ai/mcp-server stays online.
> Also, {{generate-catalog.sh}} lists the files of an example as found on disk,
> so files written by a local run (such as {{parked/}} or {{inbox/}}) can end
> up in the catalog. camel-jbang-core's synced copy still lists
> {{fail-well/error-handling/parked/order-1003.json}} from such a run, which
> the bundling sync would fail on. The script should skip the files git ignores.
> After the catalog is updated, camel-jbang-core resyncs with
> {{-Psync-example-catalog}}.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
