changed application.properties not taken into account starting devmode

mvn quarkus:devmode picks up .java changes but does not pick up changes to application.properties for that I need to explicitly do mvn compile quarkus:devmode.

I would expect it to be picked up if .java changes are OR that all “compilable” source changes will be ignored by quarkus:devmode

[jaikiran]

http.port will never work, as hot replacement is based on HTTP requests. I could make it work if we really want it but I don’t really think it is worth it?

@stuartwdouglas, The only reason I can think of why the user might have changed the value is probably because that port is already being used by some other process. In that case the dev mode startup itself would (should) fail and that would mean changing the port in the application.properties will actually be hot deployed. So I personally don’t see any genuine use case where we might want to support changing this port after a successful dev mode startup. But, maybe we should at least log a WARN if we do detect this change in port during hot deployment, so that at least users are aware that the new port isn’t being used?

[stuartwdouglas]

http.port will never work, as hot replacement is based on HTTP requests. I could make it work if we really want it but I don’t really think it is worth it?