Closed scottrbrtsn closed 2 years ago
Works fine for me. Looks like something is wrong with your plugin installation or the bundles definition. If you compiled eclipse yourself, make sure you used the same JDK version for everything.
Also keep in mind that there were just a couple of new releases for the full stack and the bundle list changed. See https://github.com/microsoft/vscode-java-test/commit/54b5ad5459e102ba64ecb217ee74e4f24a0e3de9
Given that you're using globs it should be fine, but you can double check by listing your actual bundles:
:lua =vim.lsp.get_active_clients()[1].config.init_options.bundles
Here are mine for reference:
/java-debug/com.microsoft.java.debug.plugin/target/com.microsoft.java.debug.plugin-0.40.0.jar",
/vscode-java-test/j[...]/target/com.microsoft.java.test.plugin-0.37.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-jupiter-api_5.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-jupiter-engine_5.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-jupiter-migrationsupport_5.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-jupiter-params_5.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-platform-commons_1.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-platform-engine_1.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-platform-launcher_1.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-platform-runner_1.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-platform-suite-api_1.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-platform-suite-commons_1.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-platform-suite-engine_1.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/junit-vintage-engine_5.9.0.jar",
/vscode-java-test/j[...]site/target/repository/plugins/org.opentest4j_1.2.0.v20190826-0900.jar",
/vscode-java-test/j[...]site/target/repository/plugins/org.apiguardian.api_1.1.2.jar",
/vscode-java-test/j[...]site/target/repository/plugins/org.eclipse.jdt.junit4.runtime_1.3.0.v20220609-1843.jar",
/vscode-java-test/j[...]site/target/repository/plugins/org.eclipse.jdt.junit5.runtime_1.1.0.v20220715-1030.jar",
/vscode-java-test/j[...]site/target/repository/plugins/org.opentest4j_1.2.0.v20190826-0900.jar"
ok that's something...I pulled latest and rebuilt vscode-java-test
but then trying to list bundles I get {"",""}
There’s a cluster of issues but now I see.
It seems I needed the latest from vscode-Java-test. Im good this can be closed.
Missed the latest commit by like 1 day… LOL
LSP client configuration
Ftplugin/Java.lua
Eclipse.jdt.ls version
No response
Steps to Reproduce
after you installing vscode java-test and Java-debug. DAP seems to work fine.
In project
junit5-Jupiter-started-gradle
From junit-samplesnvim .
:lua reqire’jdtls’.test_nearest_method()
Expected Result
The test would run
Actual Result
JdtShowLogs