davsclaus opened a new pull request, #28874: URL: https://github.com/apache/camel/pull/28874
_Claude Code on behalf of davsclaus_ [CAMEL-26494](https://issues.apache.org/jira/browse/CAMEL-26494) `camel run --dev --source-dir` watches every file under the source directory, except the data folders of `--data-dir` (CAMEL-25670). A Citrus test of the project, such as `test/orders.citrus.it.yaml` (the layout of camel-jbang-examples, run with `camel test run`), is not a route, yet each change of it reloaded the routes ("Routes reloaded summary (total:1 started:1 changed:0)"), which restarted every route for nothing. ### Changes - `RunPipeline.sourceDirReloadPattern` adds `!**/*.citrus.*` to the pattern, next to the data-folder excludes. The same pattern is used by the Camel Main runner of the exported project (`CamelMainRunner.reloadArgs`). - No change in `camel-support`: the `!` excludes of CAMEL-25670 already match by file name and by relative path. The folder holding the tests is still walked, so a route next to them is still watched. - Docs: a short note in the "Data folders in the source directory" section of `camel-jbang-running.adoc`. At startup a Citrus test file loads no routes already (it gets a no-op loader), so only the reload was affected. ### Tests - `RunTest.sourceDirReloadPatternLeavesTheDataDirsOut`: the expected patterns now include the Citrus exclude. - `RouteWatcherReloadDataDirTest.testCitrusTestsAreNotWatched` (camel-core): with that pattern, a test at the top or under `test/`, new or changed, is no change; a route in the same folder still is. Ran `RouteWatcherReloadDataDirTest` (8 tests) and `RunTest` (24 tests), all green. Not tried in a live `camel run --dev` session. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_0128ThHB3iQdrvSRLVBGRrdP -- 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]
