-
Notifications
You must be signed in to change notification settings - Fork 350
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
Junit project: Cannot determine executable for debug adapter '{0}' #167
Comments
I have the same after updating to VSCode 1.18.1. I downgraded to VSCode 1.18.0, but am still experiencing the issue. My environment: macOS Sierra: 10.12.6 VSCode extensions: java -version
|
No idea why, but this fixed it for me.
This is working with VS Code 1.18.1. |
Reproduced this bug on my windows 10 machine. I enabled the language server in debug mode, and found [Marker [on: /10.junit, id: 3, type: org.eclipse.buildship.core.gradleprojectconfigurationmarker, attributes: [message: Missing Gradle project configuration folder: .settings, severity: 2], created: 11/20/17 10:50 AM]] The java debugger just shows @ansyral Refer to the eclipse behavior, if there are problems in workspace, should pop up a message box to allow user to |
@testforstephen How do you enable the language server in debug mode ? I have the same error on my linux box. When i open up my project using eclipse i don't get any errors |
@GrubbyHalo There are two ways to launch language server in debug mode.
so if i run java debugger in You can download language server and java debug server source code from github, and attach to 1044 port to debug the extension code.
|
Well this is bizarre. I fired up the extension in development mode and got the same error i got above while trying to debug it. No other meaningful messages. I then closed the extension dev host and on a whim removed the eclipse generated folders in my workspace (I used eclipse for this project before trying vscode) and tried debugging the project again and it worked! no error messages. I thought that maybe the eclipse generated folders might be responsible in some way for the errors so to test the theory i put them back again, but still got no errors! So now i am not sure what fixed it. |
@GrubbyHalo Refer to #170, @wokhan provides a workaround, that should work. |
@testforstephen In fact the workaround I reintroduced was already there in the previous version of the extension (0.3.0), and has been "removed" (i.e. uncommented) by @andxu for 0.3.1 when RedHat Java support extension was upgraded to 0.14, so I guess there was a good reason for this. |
Fixed on PR: #176 |
On windows 10 I solved it like this:
My version is 1.19.3 |
Environment
Steps To Reproduce
[attach a sample project reproducing the error]
10.junit.zip
Current Result
The text was updated successfully, but these errors were encountered: