davsclaus opened a new pull request, #94: URL: https://github.com/apache/camel-jbang-examples/pull/94
[CAMEL-25261](https://issues.apache.org/jira/browse/CAMEL-25261) ## Bundle the examples of the ladder that run offline This sets `"bundled": true` on 19 examples that need no Docker, no API key and no network: | Group | Examples | |---|---| | 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 | Together with the 8 bundled today, the Camel CLI ships the whole ladder from quick-start to contracts, about 115 KB more. The examples then run offline with `camel run --example`, in the TUI example browser and through the MCP tools. `ai/mcp-server` stays online for now. ## The catalog skips the files git ignores `generate-catalog.sh` listed an example's files as found on disk. A file written by a local run, such as `parked/` or `inbox/`, could therefore end up in the catalog. One such file is still listed in the copy camel-jbang-core synced on 19 Sept. The download skips it, but the bundling sync in camel-jbang-core fails on it. The script now leaves out what `git ls-files --others --ignored --exclude-standard` reports. I checked it with a stray `fail-well/error-handling/parked/leftover.json` on disk: the file stays out of the catalog. The regenerated catalog differs from `main` only in the 19 `bundled` flags. After merge, camel-jbang-core resyncs with `-Psync-example-catalog`. _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]
