Jinbo Wang

> > The correct vscode term is the inline breakpoints, which can be added today even thought they are treated as normal line breakpoints. > > It works in VS...

> @testforstephen i think setting a line breakpoint in java debugger stops on all locations in that line. Have a look again, VS Code Java Debugger provides the same behavior....

Thanks for the information. I can reproduce it, it's a bug.

Opened an issue at the upstream JDT. https://bugs.eclipse.org/bugs/show_bug.cgi?id=578148

@tracyntimothy Thanks for reaching out. Do you mean the breakpoints are skipped during debugging? And would you mind sharing the full snippet for us to investigate the issue?

https://github.com/microsoft/vscode-java-debug/blob/a3f48af1513c9b293a50b465dc43d9315b58bc58/package.json#L377-L385 Usually when adding a new property to launch configuration, we update package.json to include the new property schema definition as well. See the sample for `mainClass` above. This can...

Could you pls provide the steps how to reproduce it?

@dsyer thanks for reaching out. yes, it's an issue with vscode-java extension, the debugger is reusing the same build output from vscode-java extension. Looks like it doesn't copy the resources...

This issue only happens when the file Main.java is standalone Java file.

When the project name is not specified, the debugger will determine the project from the main class name. The approach is to use search engine to get the IJavaElement first,...