You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I face a situation where changing an xml resources should trigger a quarkus dev restart while it's not the case.
Expected behavior
I would expected the dev mode to restart the service.
Actual behavior
The service is not restarted.
To Reproduce
git clone git@github.com:aldettinger/quarkus-devmode-restdsl-not-reloaded-reproducer.git
mvn quarkus:dev
http :8080/steps (output STEP 1 => ok)
In rests.xml, change "STEP 1" to "STEP 2" and save
http :8080/steps (output STEP 1 => ko)
Sometimes, no change is detected.
Sometimes, it displays "Files changed but restart not needed - notified extensions".
While any change in application.properties make the application reloaded which is great.
Is is possible that an xml resource always trigger reload like an application.properties file ? Via configuration ? Via an extension that would mark this file as restartNeeded ?
The closest issue I found is #16350, but not sure there is a link.
The text was updated successfully, but these errors were encountered:
Many thanks @famod , it works like a charm to set it via configuration 👍
Now, I wonder what would be the correct way to handle this from an extension, maybe having an extension adding configuration is ok.
Describe the bug
I face a situation where changing an xml resources should trigger a quarkus dev restart while it's not the case.
Expected behavior
I would expected the dev mode to restart the service.
Actual behavior
The service is not restarted.
To Reproduce
git clone git@github.com:aldettinger/quarkus-devmode-restdsl-not-reloaded-reproducer.git
mvn quarkus:dev
http :8080/steps (output STEP 1 => ok)
In rests.xml, change "STEP 1" to "STEP 2" and save
http :8080/steps (output STEP 1 => ko)
Sometimes, no change is detected.
Sometimes, it displays "Files changed but restart not needed - notified extensions".
While any change in application.properties make the application reloaded which is great.
Is is possible that an xml resource always trigger reload like an application.properties file ? Via configuration ? Via an extension that would mark this file as restartNeeded ?
The closest issue I found is #16350, but not sure there is a link.
The text was updated successfully, but these errors were encountered: