Maven projects not loading in VS Code after latest Language Support for Java by Red Hat Extension Update (v1.42.0)

After updating the Language Support for Java(TM) by Red Hat extension to version 1.42.0 (2025-05-19), my Maven Java projects no longer load properly in Visual Studio Code. The Java Language Server fails to resolve standard Java classes (e.g., java.lang.Object), and the Maven projects are not recognized or built correctly.

To Reproduce
Steps to reproduce the behavior:

1. Open a multi-module Maven Java project in VS Code.
2. Ensure the latest Language Support for Java(TM) by Red Hat extension (v1.42.0) is installed.
3. Set the JDK in VS Code settings (settings.json) to JDK 8, 11, or 21 (tried all):
   "java.jdt.ls.java.home": "valid\path\to\jdk"
4. Reload VS Code.
5. Observe that Maven projects are not loaded, and Java standard library classes cannot be resolved.

Error Logs

1. The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
2. Unbound classpath container: 'JRE System Library [java-21-openjdk]' in project ...

Environment (please complete the following information):

• OS: Windows 10/11
• VS Code version: [1.100.2]
• Language Support for Java(TM) by Red Hat extension version: 1.42.0
• JDK versions tried: 8, 11, 21 (paths set correctly in settings)
• Maven version: [3.6.0]

Additional context

• The issue started after updating to extension v1.42.0.
• The same project setup worked with previous extension versions.
• Tried cleaning workspace, deleting .classpath/.settings, and reinstalling the extension, but the issue persists.

Steps already tried

• Changed JDK versions and updated settings.json
• Set JAVA_HOME and updated PATH
• Cleaned and rebuilt Maven projects
• Reinstalled Java extensions
• Restarted VS Code and the system

Reproduzieren Sie das Problem mit dem Multi-Modul-Maven-Projekt, VS Code 1.100.2, der Erweiterung 1.42.0 und den JDK-Einstellungen in settings.json; beginnen Sie mit den Fehlern des Java Language Server und den .classpath/.settings-Dateien des Projekts. Als erledigt gilt die Aufgabe, wenn Maven-Projekte korrekt geladen werden und Standardklassen wie java.lang.Object ohne eine unbound JRE System Library aufgelöst werden.