Currently, Quarkus extensions (runtime artifacts) are always excluded from live reload in dev mode (DependenciesFilter marks them as non-reloadable). This means template/CSS/resource changes in an extension require a full mvn install + dev server restart.
For extensions that provide templates and static resources (e.g., theme extensions, UI component libraries), this creates a slow development loop. The extension's Java code doesn't need reloading, but its resources (templates, CSS, JS) should be watchable.
quarkus.live-reload.watched-resources doesn't help because RuntimeUpdatesProcessor only scans reloadable modules.
Proposal: Allow extensions to opt-in to resource-level live reload, either through:
- A build-time config to list extension artifacts whose resources should be watched
- An extension metadata flag indicating its resources are safe to reload without recompilation
Use case: Roq has theme extensions providing Qute templates and CSS. During theme development, every template tweak requires a full rebuild cycle.
Currently, Quarkus extensions (runtime artifacts) are always excluded from live reload in dev mode (
DependenciesFiltermarks them as non-reloadable). This means template/CSS/resource changes in an extension require a fullmvn install+ dev server restart.For extensions that provide templates and static resources (e.g., theme extensions, UI component libraries), this creates a slow development loop. The extension's Java code doesn't need reloading, but its resources (templates, CSS, JS) should be watchable.
quarkus.live-reload.watched-resourcesdoesn't help becauseRuntimeUpdatesProcessoronly scans reloadable modules.Proposal: Allow extensions to opt-in to resource-level live reload, either through:
Use case: Roq has theme extensions providing Qute templates and CSS. During theme development, every template tweak requires a full rebuild cycle.