Improve automatic reload on Camel route
- Dominant language
- Java
- Stars
- 302
- Forks
- 232
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 114
Description
### Describe the feature here
reloading a relatively simple Camel route is taking 6 seconds (on my machine).
a log is suggesting some ways to have small changes ot be faster (like in my case changing the content of a string in a log message):
```
2025-11-07 18:02:58,992 INFO [io.qua.dep.dev.RuntimeUpdatesProcessor] (Timer-0) Live reload took more than 4 seconds, you may want to enable instrumentation based reload (quarkus.live-reload.instrumentation=true). This allows small changes to take effect without restarting Quarkus.
```
(and yes I realize that there can be a lot of different use cases and a lot of work but maybe some quick win available?)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported six-second reload for a simple Camel route and examine the RuntimeUpdatesProcessor log and the quarkus.live-reload.instrumentation setting mentioned in the issue. Establish which small route changes should reload faster, then define and measure a successful improvement; the issue currently names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100