[
https://issues.apache.org/jira/browse/CAMEL-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078191#comment-18078191
]
Claudio Miranda commented on CAMEL-23293:
-----------------------------------------
Unfortunately spring devtools only detect changes in target/classes, so when
the user changes the .java file, somehow a compilation must be triggered, but
devtools lacks this. Quarkus plugin has this feature but not the spring
devtools, so that's why it doesn't work the way we want in camel jbang. There
is a "fizzed" maven plugin that could do it, but it doesn't work.
> [camel-jbang] Files are not synched in dev-mode with Quarkus runtime
> --------------------------------------------------------------------
>
> Key: CAMEL-23293
> URL: https://issues.apache.org/jira/browse/CAMEL-23293
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Affects Versions: 4.18.1
> Reporter: Simon Hartl
> Assignee: Claudio Miranda
> Priority: Minor
> Fix For: 4.21.0
>
>
> According to the documentation the '--dev' flag should also allow hot-reload
> when using the Quarkus runtime.
> However when I run a route with the following command the hot-reload hence
> dev-mode doesn't work.
> {{camel run --dev --runtime=quarkus testroute.camel.yaml}}
> I did see that a temp-directory within '.camel-jabng-run' is created which
> contains the route. Also the Quarkus project itself is run with the
> 'quarkus:dev' target as changing the file
> '.camel-jabng-run/.../src/main/resources/camel/testroute.camel.yaml' does
> auto-reload.
> But it seems the 'testroute.camel.yaml' isn't synced into the
> '.camel-jabng-run/.../src/main/resources/camel' directory on change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
