Skip to content

Remote dev not reloading on changes in workspace library #51426

@xjarvik

Description

@xjarvik

Describe the bug

When running mvn quarkus:remote-dev against a remote application, changes made in a library (in my workspace) do not cause an automatic reload of the remote application. The live-reload functionality does however work fine when running mvn quarkus:dev. Changes inside the main application code do cause a reload in both local dev and remote dev.

I can see the following output before Quarkus connects to the remote app:

[WARNING] [io.quarkus.bootstrap.devmode.DependenciesFilter] Live reload was disabled for the following project artifacts:
- org.example:my-lib:1.0.0-SNAPSHOT
The artifacts above appear to be either dependencies of non-reloadable application dependencies or Quarkus extensions

I don't know exactly what "non-reloadable application dependency" implies and what the difference is between local dev and remote dev regarding live-reload of libraries. I assumed they should work the same but maybe this assumption is wrong. I have followed the remote-dev guide. My remote app runs inside a kubernetes cluster and I can see that it connects without issue.

Both the main app and the library are inside the same maven project. See https://github.com/xjarvik/remote-dev-live-reload.

Expected behavior

The remote application should reload on changes in a library.

Actual behavior

The remote application does not reload when changes are made in the library. Changes in the main app do however cause a reload.

How to Reproduce?

https://github.com/xjarvik/remote-dev-live-reload

Output of uname -a or ver

No response

Output of java -version

25.0.1

Quarkus version or git rev

3.30.2

Build tool (ie. output of mvnw --version or gradlew --version)

Maven 3.9.6

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions