The same name class exist in the same package, but "type is already defined" error will auto disappear

[hhkrob1]

[provide a description of the issue]

Environment

• Operating System: Windows 11
• JDK version: OpenJDK 17 and JDK1.8
• Visual Studio Code version: 1.64.2
• Java extension version: 1.3.0

Steps To Reproduce

1. When the same name class exist in the same package, click run in codelen, compile will not pass, problem pannel will display "type is already defined" error, click this navigation to related code line, the error(Red wavy line) auto disappear and never show again. but it is a error, it will be always warnning.
2. Related gif:
   

[Please attach a sample project reproducing the error]
Please attach logs

Current Result

When the same name class exist in the same package, it is a error, it will be always warnning, navigation to relative code line, the error auto disappear and never show again until reopen VScode next time.

Expected Result

When the same name class exist in the same package, it is a error, it will be always warnning.

Additional Informations

[cworld1]

Same problem.

[rgrunber]

I just noticed this is a duplicate of #1111. I explain what's happening at #1111 (comment) (and the previous comment). The way we collect diagnostics has a risk of hiding diagnostics at the file-level that can only be reported through a full compilation.

There may be a few ways to avoid this happening.