How can I fix build failed, do you want to continue? in vscode

Update. Problem solved I resolved this issue by clearing the workspace cache in VS code. Here is a link to the relvant page: VSCODE Clean Workspace Directory . I had renamed a number of folders, class names and packages. Apparently the RedHat-Developer plugin managed to get out of sync. The .classpath file was out of sync with the POM file. Wiping out the workspace cache caused the plugin to recreate project data from the maven spec. Problem solved. Not sure but if anyone from the RedHat project reads this, it looks to me like a bug, or deficiency. In any event it can be worked around.

Original answer follows:

I think Liu Bei was not clear enough. I am experiencing the same issue. I have a project that builds perfectly in Maven and when I launch the debugger in Visual Studio Code this notification appears in the lower right-hand corner of the VSCode window.

Obviously the "Debugger for Java" extension thinks there is a build problem. However there are no errors reported in the PROBLEMS, OUTPUT, DEBUG CONSOLE or TERMINAL tabs.

The project builds, and packages in Maven just fine and it can be debugged in attach mode which is tedious at best.

There is something going on in VSCode that's not being reported anywhere that I can find. I suspect the RedHat VSCode plugin for Java is in the mix but need help figuring out how to work around the issue.

I have to say that we are spending way too much time resolving issues with tools and dependencies and not enough time on the app. The project we are working on is intended for open source distribution. The Spring Framework seems ideal for our purposes but the tooling, not so much. We are not very far into the project and I am already receiving pressure to switch to .NET core MVC.

Really need a little help...

So this didn't work for me, but I found out what did.

First of all looking at the Java Dependencies plugin gave me a hint that something was out of sync. The name of my application (artifact) did not match the name in the Java Dependencies tree view.

This was fixed by clearing the VSCode workspaceStorage folder completely!

This folder was in my case located in (Windows 10):

C:\Users\<myuser>\AppData\Roaming\Code\User\workspaceStorage

If you can't find it at this location, simply search for the folder workspaceStorage.

Next press ctrl + shift + p (in my case) to open the VSCode action prompt. Then choose the command:

Java: Open Java Language Server Log File

This will open a log file which is normally not displayed when building your Java code, and will tell you exactly what went wrong with the build.

In my case it was a conflict as I had two AppConfig.java files, one in main and one in test. Maven handles this fine, but apparently the VSCode Java builder does not.

Obviously these are bugs in the plugins which I will report to the GitHub contributors, but for now we will have to live with a little manual work.

Still I hope this helps all of you frustrated VSCode Java developers out there.

It worked for me to change the user setting in setting.json to "java.debug.settings.forceBuildBeforeLaunch": false on vscode, which will disable the check before run/debug.