You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unzip the attached project.zip file into an otherwise empty directory
Start code bug.code-workspace
Click that you trust the author of this workspace (to enable debugging)
Ensure that no text editors are open for any files
Observe that no problems are reported in the Problems pane
Open the file src/test/java/com/example/QuxTest.java from the Explorer pane
Right-click the triangular play icon next to public class QuxTest
Choose Debug Test from the context menu
Notice that a problem appear in the Problems pane for file Foo.java
"The method b() is undefined for the type Mumble"
Click on the problem to open file src/main/java/com/example/Foo.java
Notice that the problem disappears by itself
Current Result:
Debugging of unit tests halts on an imaginary problem.
Expected Result:
Unit test should launch without any reported errors.
Additional Informations:
I reckon that this problem is related to annotation processing inserting stubs for the depended-on classes, and then these stubs aren't resolved properly. This may be a bug in the language server instead of the extension.
This looked like it was caused by the debugger, but as of VSCode 1.82.2 it is also triggered when the project loads outside of the debugger, so it is moved to redhat-developer/vscode-java#3302.
Environment
Steps To Reproduce
code bug.code-workspace
public class QuxTest
"The method b() is undefined for the type Mumble"
Current Result:
Debugging of unit tests halts on an imaginary problem.
Expected Result:
Unit test should launch without any reported errors.
Additional Informations:
I reckon that this problem is related to annotation processing inserting stubs for the depended-on classes, and then these stubs aren't resolved properly. This may be a bug in the language server instead of the extension.
project.zip
The text was updated successfully, but these errors were encountered: