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
{{ message }}
Repository navigation
Maven projects not loading in VS Code after latest Language Support for Java by Red Hat Extension Update (v1.42.0) #4054
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:
Open a multi-module Maven Java project in VS Code.
Ensure the latest Language Support for Java(TM) by Red Hat extension (v1.42.0) is installed.
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"
Reload VS Code.
Observe that Maven projects are not loaded, and Java standard library classes cannot be resolved.
Error Logs
The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
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.
I had the same issue and tried lots of things to make it work, including cleaning the workspace, deleting workspaceStorage, reinstalling extensions ... Finally, I changed the project directory name, and it worked. Fxxk.
Activity
hubeizys commentedon Jun 17, 2025
I had the same issue and tried lots of things to make it work, including cleaning the workspace, deleting workspaceStorage, reinstalling extensions ... Finally, I changed the project directory name, and it worked. Fxxk.
palminha commentedon Jul 4, 2025
@ccoderonline was it solved with version 1.43.1?