You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to implement some other commands available in Eclipse JDT Debugger. I have forked the repository. However when I try to debug the extension I always run into:
No delegateCommandHandler for vscode.java.startDebugSession
Reloading VSCode does not help as has been indicated elsewhere.
BTW I also tried to build vsix package and install it. That runs into same issue.
Will restarting JLS help? Or may be disable enable extentions?
I think this has something to do with the order of activation of extensions. Is there a way to control the order of activation of extension?
Is the correct way to develop this extension documented here.?
The strong motivation for this for me is that I can truly switch over to VS Code for Java development.
All Instances
All References
Open Actual Type
Open Declared Type
Environment
Operating System:
JDK version:
Visual Studio Code version:
Java extension version:
Java Debugger extension version:
Steps To Reproduce
Clone the repo
npm install etc
Debug the extension using F5
Current Result
See this exception in Extension Host log:
No delegateCommandHandler for vscode.java.startDebugSession