When running tests on my java project in vscode I would get a pop-up warning saying "build failed" and giving me options to continue, always continue, or fix. I accidentally clicked always continue so the pop-up doesn't show anymore. I want to make the pop-up come back.
I have tried the solution at How can I reenable the warning about unsupported Python version by VS Code debugger but I couldn't find the setting I needed. I also tried completly uninstalling and reinstalling vscode following the instructions here how to completely remove vs-code setting?. The latter did restore a bunch of other pop-ups but not the build failed pop-up I want.
I am using gradle version 8.8 and the debugger for java by microsoft
When running tests on my java project in vscode I would get a pop-up warning saying "build failed" and giving me options to continue, always continue, or fix. I accidentally clicked always continue so the pop-up doesn't show anymore. I want to make the pop-up come back.
I have tried the solution at How can I reenable the warning about unsupported Python version by VS Code debugger but I couldn't find the setting I needed. I also tried completly uninstalling and reinstalling vscode following the instructions here how to completely remove vs-code setting?. The latter did restore a bunch of other pop-ups but not the build failed pop-up I want.
I am using gradle version 8.8 and the debugger for java by microsoft
Share Improve this question edited Mar 24 at 21:27 user29980463 asked Mar 20 at 11:39 user29980463user29980463 13 bronze badges 1- please add extension ID and version – starball Commented Mar 21 at 9:41
3 Answers
Reset to default 0You want to set the java.debug.settings.onBuildFailureProceed setting back to false, or remove it from your user settings.json file so it goes back to the default value of false.
Uninstalling VS Code didn't reset this because uninstalls intentionally do not remove user configuration files.
You need to untick the box in the picture.
.
No idea how this setting survived an uninstall and reinstall but there you have it.
Check once in vscode where the maven build or plugin is there,see whether the compiler warnings is checked or non checked ,if its checked it might come,so the place from where you are building the project that plugin's settings needs to be verified once