Annotation processing causes spurious reporting in Problem pane

Environment

• Operating System: Ubuntu Focal 20.04.6
• JDK version: 17.0.7
• Visual Studio Code version: 1.82.2
• Extensions:
  • vscjava.vscode-java-pack 0.25.14
  • vscjava.vscode-java-debug 0.54.0
  • redhat.java 1.22.1
  • vscjava.vscode-maven 0.42.0
  • vscjava.vscode-java-dependency 0.23.1
  • vscjava.vscode-java-test 0.39.1

Steps To Reproduce

0. Unzip the attached project.zip file into an otherwise empty directory
1. Start code bug.code-workspace
2. Ensure that a text editor is not open for Foo.java
3. Click that you trust the author of this workspace (to enable debugging)
4. Observe that no problems are reported in the Problems pane
5. Open the file src/test/java/com/example/QuxTest.java from the Explorer pane
6. Right-click the triangular play icon next to public class QuxTest
7. Choose Debug Test from the context menu
8. Notice that a problem appear in the Problems pane for file Foo.java:
   "The method b() is undefined for the type Mumble"
9. Click on the problem to open file src/main/java/com/example/Foo.java
10. Notice that the problem disappears by itself as the editor for Foo.java opens
11. Close the editor for Foo.java
12. Exit VSCode
13. Restart VSCode, as in point 1.
14. Observe that the problem reappears in the Problem pane, this time without opening the debugger.

Current Result:

A problem is reported for the class used in an annotation.

Expected Result:

No problems should be reported.

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. It started to appear related to the debugger a couple of minor versions ago, but from 1.82.2 it also happens every time the project is loaded, after it has been triggered by the debugger initially.

@testforstephen In microsoft/vscode-java-debug issue #1247 you asked for a minimal example. This looks a lot like it is related, so maybe this could be used?

project.zip

Estrai project.zip e segui la riproduzione numerata di VS Code, confrontando le diagnosi di Problems-pane prima e dopo Debug Test e il riavvio. Usa Foo.java e QuxTest.java come caso minimo; il lavoro è completato quando la classe utilizzata dall’annotazione non produce più il problema “method b() is undefined for the type Mumble” in nessuno dei due flussi.