Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Referenced classpath provider does not exist (Buildship) #3249

Open
steffsommer opened this issue Aug 23, 2024 · 0 comments
Open

Referenced classpath provider does not exist (Buildship) #3249

steffsommer opened this issue Aug 23, 2024 · 0 comments

Comments

@steffsommer
Copy link

In a Gradle project that includes another gradle build, an error is thrown that the buildship classpath provider does not exist. Happens in my personal config, but is more easily reproducible using LazyVim. LazyVims JDTLS configuration: https://github.com/LazyVim/LazyVim/blob/main/lua/lazyvim/plugins/extras/lang/java.lua.

The error leads to wrong diagnostics being displayed on the imports of the included build. Imports of the included build get the diagnostic error The import <import> cannot be resolved, although going to the definition of the import works fine.

  • jdtls : 1.38.0
  • Client: Neovim 0.10.1
  • java-test: 0.41.1
  • java-debug-adapter: 0.58.0
[ERROR][2024-08-23 07:03:24] ...lsp/handlers.lua:623	'Aug 23, 2024, 7:03:24 AM Problems occurred when invoking code from plug-in: "org.eclipse.jdt.ls.core".\nFailed to resolve classpath: Referenced classpath provider does not exist: org.eclipse.buildship.core.classpathprovider
java.lang.Exception: Failed to resolve classpath: Referenced classpath provider does not exist: org.eclipse.buildship.core.classpathprovider
com.microsoft.java.debug.plugin.internal.ResolveClasspathsHandler.resolveClasspaths(ResolveClasspathsHandler.java:79)
com.microsoft.java.debug.plugin.internal.JavaDebugDelegateCommandHandler.executeCommand(JavaDebugDelegateCommandHandler.java:62)
org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler$1.run(WorkspaceExecuteCommandHandler.java:230)
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
org.eclipse.jdt.ls.core.internal.handlers.WorkspaceExecuteCommandHandler.executeCommand(WorkspaceExecuteCommandHandler.java:220)\n\tat org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$4(JDTLanguageServer.java:606)
org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:87)
java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:646)
java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by: org.eclipse.core.runtime.CoreException: Referenced classpath provider does not exist: org.eclipse.buildship.core.classpathprovider\n\tat org.eclipse.jdt.launching.JavaRuntime.abort(JavaRuntime.java:1870)\n\tat org.eclipse.jdt.launching.JavaRuntime.abort(JavaRuntime.java:1855)
org.eclipse.jdt.launching.JavaRuntime.getClasspathProvider(JavaRuntime.java:1181)
org.eclipse.jdt.launching.JavaRuntime.computeUnresolvedRuntimeClasspath(JavaRuntime.java:1659)
com.microsoft.java.debug.plugin.internal.ResolveClasspathsHandler.computeClassPath(ResolveClasspathsHandler.java:231)
com.microsoft.java.debug.plugin.internal.ResolveClasspathsHandler.computeClassPath(ResolveClasspathsHandler.java:211)
com.microsoft.java.debug.plugin.internal.ResolveClasspathsHandler.computeClassPath(ResolveClasspathsHandler.java:165)
com.microsoft.java.debug.plugin.internal.ResolveClasspathsHandler.resolveClasspaths(ResolveClasspathsHandler.java:76)
... 13 more\n'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant