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
[1.57.0] Java projects on network drives are not recognized #4550
After upgrading Language Support for Java(TM) by Red Hat to version 1.57.0:
Creating a new Java project in a local folder works correctly.
Creating a new Java project on a network drive creates the project files, but VS Code reports that no Java projects are found and prompts me to create a new Java project.
After downgrading the extension to version 1.56.0, the issue disappears.
Expected behavior:
Java projects on network drives should be recognized correctly, just like local projects.
I'm hitting the same problem on 1.57.0 (JDT LS 1.62.0), with an existing Maven project rather than a new one. Downgrading to 1.56.0 fixes it.
Setup: Windows, folder opened as X:\...\project, where X: is a mapped drive for \\<server>\<share>. The Maven project is in a subfolder (project\project-java\pom.xml), and there is only one pom.xml in the workspace.
Symptoms:
Java Projects view: "No Java projects found in the current workspace"
Main class reported as "a non-project file, only syntax errors are reported"
Run does nothing
Log:
Importing Maven project(s)
Failed to import Maven project at \\<server>\<share>\...\project\project-java\pom.xml - a project with the same name already exists (check for duplicate groupId/artifactId)
Build projects fail: Cannot find projects from given uris. []
"Java: Import Java Projects into Workspace" shows: "1 Maven project(s) could not be imported due to duplicate groupId/artifactId."
Notes: the log shows the project under the UNC path, while VS Code uses the drive letter. Opening the folder directly through the UNC path also failed on 1.57.0, and cleaning the language server workspace did not help.
Activity
menthil commentedon Oct 19, 2026
I'm hitting the same problem on 1.57.0 (JDT LS 1.62.0), with an existing Maven project rather than a new one. Downgrading to 1.56.0 fixes it.
Setup: Windows, folder opened as
X:\...\project, where X: is a mapped drive for\\<server>\<share>. The Maven project is in a subfolder (project\project-java\pom.xml), and there is only one pom.xml in the workspace.Symptoms:
Log:
"Java: Import Java Projects into Workspace" shows: "1 Maven project(s) could not be imported due to duplicate groupId/artifactId."
Notes: the log shows the project under the UNC path, while VS Code uses the drive letter. Opening the folder directly through the UNC path also failed on 1.57.0, and cleaning the language server workspace did not help.