sts4
sts4 copied to clipboard
[exception from inside jdt ls] ResponseErrorException: Request <REDACTED: user-file-path> failed with message
java.util.concurrent.CompletionException: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Request <REDACTED: user-file-path> failed with message: command 'vscode-spring-boot.ls.start' not found
at java.base/java.util.concurrent.CompletableFuture.reportJoin(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture.join(Unknown Source)
at org.eclipse.jdt.ls.core.internal.JavaClientConnection.executeClientCommand(JavaClientConnection.java:89)
at org.springframework.tooling.jdt.ls.extension.JdtLsExtensionPlugin.lambda$2(JdtLsExtensionPlugin.java:47)
at org.springframework.tooling.jdt.ls.commons.BootProjectTracker.fireEvent(BootProjectTracker.java:72)
at org.springframework.tooling.jdt.ls.commons.BootProjectTracker.processProject(BootProjectTracker.java:60)
at org.springframework.tooling.jdt.ls.commons.BootProjectTracker.<init>(BootProjectTracker.java:51)
at org.springframework.tooling.jdt.ls.extension.JdtLsExtensionPlugin.lambda$1(JdtLsExtensionPlugin.java:57)
at java.base/java.util.
Okay, this one i understand how it might occur. Java and Boot extensions are installed. Java is activated but Boot is not. Yet the JDT LS extension from boot is already hooked up and working via JDT LS. Something became a boot project and the command to start the LS needs to be executed but it is not yet there since the extension is not "fully" activated as there is an async piece to it. We'd have to carefully re-arrange things in the extension activation logic.
Ok, so we will not tackle this one for the 5.0.0 release, I will put this on the list for 5.1.0 then.