-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure that Java code changes get picked after the class compilation #7068
Comments
The test permutations:
|
CDI investigationUsing
|
Hotswap is totally broken: it's not able to reload app because it reruns servlet context initializer which reregister the same routes. |
When building apps, I want my Java code changes to automatically get picked up after compilation and I can see the changes in the browser.
Class compilation: it's something that required for (any) tool to reload.
In fact: Java code changes should be picked up once the tool is able to pick those changes (it should not require explicit application restart).
What should be checked:
They should be checked with
Out of scope of this issue:
The scenario should be checked for any "hotswap" tool: jetty (via scanning interval), Spring boot dev tools, hotswap agent (is it a correct name?), JRebel.
The text was updated successfully, but these errors were encountered: