spring-projects / spring-projects/spring-tools
[exception from inside jdt ls] Resolve classpath: unable to resolve a project from
Open
@BoykoAlex is already working on this.
Since Oct 22, 2025.
for: eclipse
status: needs-validation
type: bug
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
java.lang.Exception: Resolve classpath: unable to resolve a project from : <REDACTED: user-file-path>
at org.springframework.tooling.jdt.ls.commons.resources.ResourceUtils.getProject(ResourceUtils.java:66)
at org.springframework.tooling.jdt.ls.commons.resources.ResourceUtils.getJavaProject(ResourceUtils.java:37)
at org.springframework.tooling.jdt.ls.commons.java.JavaData.findElement(JavaData.java:79)
at org.springframework.tooling.jdt.ls.commons.java.JavaData.typeData(JavaData.java:67)
at org.springframework.tooling.jdt.ls.extension.JavaTypeHandler.executeCommand(JavaTypeHandler.java:30)
at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler$1.run(WorkspaceExecuteCommandHandler.java:230)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
at org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler.executeCommand(WorkspaceExecuteCommandHandler.java:220)
at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$4(JDTLanguageServer.jav
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.