davsclaus opened a new pull request, #24492:
URL: https://github.com/apache/camel/pull/24492

   _Claude Code on behalf of davsclaus_
   
   ## Summary
   
   Reorganize bundled CLI/TUI examples into topic-based subfolders for better 
discoverability. This is the companion PR to 
https://github.com/apache/camel-jbang-examples/pull/70 which reorganizes the 
external examples repo.
   
   ### Changes
   - **Moved 13 bundled examples** into categorized folders: `beginner/`, 
`eip/`, `database/`, `language/`, `observability/`, `transformation/`
   - **Added 3 new EIP examples** (inspired by Citrus integration test 
patterns):
     - `eip/content-based-router` — temperature sensor with choice/when routing
     - `eip/splitter` — split comma-separated batch into individual messages
     - `eip/aggregator` — collect messages into batches using 
StringAggregationStrategy
   - **Updated catalog JSON** with new paths for all 29 examples
   
   ### Folder structure (alphabetical on GitHub)
   ```
   ai/              beginner/        cloud/           database/
   eip/             language/        messaging/       observability/
   rest/            security/        transformation/
   ```
   
   `beginner/` sorts first, giving new users a clear starting point.
   
   ### Dependency
   Merge https://github.com/apache/camel-jbang-examples/pull/70 first — online 
examples will 404 until the external repo has the new folder paths.
   
   ## Test plan
   - [x] All 3 new YAML routes validate against Camel YAML DSL schema
   - [x] `mvn clean install -DskipTests` passes for `camel-jbang-core`
   - [x] JAR contains only the new categorized paths (no stale flat paths)
   - [ ] Run `camel run --example=beginner/timer-log` after both PRs merged
   
   Co-Authored-By: Claude Opus 4.6 <[email protected]>


-- 
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]

Reply via email to