Repository navigation
java.debug.settings.hotCodeReplace "auto" has a wierd behaviour #1584
Description
As per title if I set java.debug.settings.hotCodeReplace to "auto" it seems to trigger the "applying code changes" multiple time, which requires more time and eventually ends up in rebuilding the entire application instead of the single modified.
I tried to look out for some kind of output or log to get core of the issue but without any success. I also tried to look out at the docs in case I messed up the settings but nothing looks out of place, except maybe for the "java.autobuild.enabled" set to true (which is not a debugger setting).
"java.debug.settings.console": "internalConsole",
"java.debug.settings.hotCodeReplace": "manual",
"java.debug.settings.forceBuildBeforeLaunch": true
Manually invoking the hot code replace works as intended (at least per my knowledge).
Activity
github-actions commentedon Nov 10, 2025
Hi Gianluca Turra (@GianlucaTurra), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
Workarounds & Suggestions
redhat.java&vscjava.vscode-java-debug)Duplicates
hotCodeReplace=auto)Other references with high confidence
Other references with low confidence
autovsmanualvsnevermodesThe team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!