Added by @jdneo:
check #1481 (comment) for the workaround.
0.37.1 has been released, the problem should be gone with the latest version.
Environment
System : Windows10, WSL2, Debian 11
JDK: OpenJDK 64-Bit Server VM (build 17.0.4+8-Debian-1deb11u1)
Gradle: 7.4.2
VSCode: v1.70.2
redhat.java: v1.10.0
vscjava.vscode-java-test: v0.37.2022083002
vscjava.vscode-java-debug: v0.43.0
Symptom
Test cannot be launched. The notification in the right bottom shows Run Tests: Resolving launch configuration forever

How to reproduce
- Create an
Application project with gradle init .
- Open the project folder with VSCode
- Open
Testing in the side panel.
- right click
appHasAGreeting() and choose Run Test.
Notes
- Running the
main of the App class from VSCode works fine.
- Running
gradle test works fine.
Added by @jdneo:
check #1481 (comment) for the workaround.0.37.1has been released, the problem should be gone with the latest version.Environment
System : Windows10, WSL2, Debian 11
JDK: OpenJDK 64-Bit Server VM (build 17.0.4+8-Debian-1deb11u1)
Gradle: 7.4.2
VSCode: v1.70.2
redhat.java: v1.10.0
vscjava.vscode-java-test: v0.37.2022083002
vscjava.vscode-java-debug: v0.43.0
Symptom
Test cannot be launched. The notification in the right bottom shows
Run Tests: Resolving launch configurationforeverHow to reproduce
Applicationproject withgradle init.Testingin the side panel.appHasAGreeting()and chooseRun Test.Notes
mainof theAppclass from VSCode works fine.gradle testworks fine.