Extension incorrectly runs cached `.class` file from another class of same name with no `package`

Bug report

Suppose there is a file structure:

folder1/
    Main.java
folder2/
    Main.java

// folder1/Main.java
public class Main {
    public static void main(String[] args) {
        System.out.println("Main 1");
    }
}

// folder2/Main.java
public class Main {
    public static void main(String[] args) {
        System.out.println("Main 2");
    }
}

No package statements; the projects are not connected at all.

When folder1/Main.java is run first, it gives the correct output Main 1.
But if folder2/Main.java is then run, it gives the wrong output of Main 1 instead of Main 2; the first built file is run instead.
folder1/Main.java 'shadows' folder2/Main.java, since the class name is the same and there are no package statements.
Another file structure that causes this is ./Main.java, ./folder/Main.java

This bug is inconvenient when multiple different, unrelated Java projects are in the same workspace.

folder1/Main.java を実行し、その後 folder2/Main.java を実行して問題を再現します。./Main.java と ./folder/Main.java のレイアウトも含めます。拡張機能がキャッシュされたコンパイル済みクラスをどのように選択するかを追跡します。完了の条件は、互いに無関係な各 Main.java が、もう一方のファイルをすでに実行した後も、それぞれ自身の出力を実行することです。