Closed gudjonragnar closed 1 year ago
Thanks for the report.
Looks like https://github.com/microsoft/vscode-java-test/commit/5a78371ad60e86f858eace7726f0980926b6c31d changed the response format. After I updated it locally it also started failing for me with the same error.
Should be fixed with https://github.com/mfussenegger/nvim-jdtls/pull/437
Ye I was about to post a follow up with that same commit. Thanks for the quick turnaround :+1:
LSP client configuration
Eclipse.jdt.ls version
1.20.0
Steps to Reproduce
I have this issue in a gradle project using Gradle 7.3.2 and Java 17.
When I run
:lua require'jdtls'.test_nearest_method()
I get an error message saying:The line in question is (line numbers above are off by one because of a print statement i added):
I decided to print the
launch_args
object and got this table:It seems like the launch_args are wrapped in this
body
table which messes things up. When I addon line 244 (on tag 0.2.0) before the classpath is extended everything works fine and the test passes.
I am not sure if I may be doing something wrong which causes the launch args to be wrapped in the body object or if there is a change in vscode.java.test that causes this.
Expected Result
Tests run and pass/fail
Actual Result