Claus Ibsen created CAMEL-26494:
-----------------------------------
Summary: camel-jbang - camel run --dev with a source directory
reloads the routes when a Citrus test of the project changes
Key: CAMEL-26494
URL: https://issues.apache.org/jira/browse/CAMEL-26494
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.24.0
{{camel run --dev --source-dir}} watches every file under the source directory,
except the data folders of --data-dir (CAMEL-25670):
{{RunPipeline.sourceDirReloadPattern}} gives {{*}} plus {{!<dataDir>/**}}.
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.
Still, each change of it reloads the routes: "Routes reloaded summary (total:1
started:1 changed:0)". This restarts every route for nothing.
It was seen in the local-model benchmark (the test-citrus-orders example),
where the model writes the test while the integration runs in dev mode. At
startup the test file loads no routes, because a file with no routes loader
gets a no-op loader. So only the reload is affected.
Proposal: leave the Citrus test files ({{*.citrus.*}}, such as
{{*.citrus.it.yaml}}) out of the reload pattern of dev mode with a source
directory, as the data folders are.
_Filed by Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
