Remote dev not reloading on changes in workspace library

[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

[quarkus-bot[bot]]

/cc @geoand (kubernetes)

[xjarvik]

I tried going back to Quarkus version 3.23.4, and with that version I do not get the warning, and changes in the library seem to sync to the remote app just fine. I also tried version 3.24.5 and that version does however give me the warning, so this issue likely appeared somewhere between those two versions.

Interestingly though, on 3.23.4 I have to set <finalName>${project.artifactId}</finalName> inside the build-section of my pom-files in order for changes to actually take effect. I actually discovered this a while back when testing remote-dev for the first time, although I don't remember exactly how I found it. I think there may be some mismatch between the name of the jar file on the remote vs the local side. Might be similar to #50516.