Claus Ibsen created CAMEL-24862:
-----------------------------------
Summary: camel-jbang - dev mode does not compile a Java class
added to the source directory while running
Key: CAMEL-24862
URL: https://issues.apache.org/jira/browse/CAMEL-24862
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Found by the stepwise half of the round-2 local-model benchmark (ten
camel-jbang-examples built step by step through the camel-jbang-mcp server,
five runs each, 2026-09-21).
With {{camel run --source-dir=. --dev}} running a YAML route, adding
{{OrderNumber.java}} and a {{beans.yaml}} that declares it as a bean, and
referencing the bean from the route, ends in "No bean could be found in the
registry for: orderNumber" and "class camel.example.OrderNumber was not found"
on every reload; a restart of the same command line loads it fine. The reload
compiles nothing new; only a restart does. Dev mode should compile a new (or
changed) Java class in the source directory on reload, the way it reloads a
changed route file, or the reload error should say that a new Java class needs
a restart.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
