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
{{ message }}
Repository navigation
Java server started when clicking on 'config launch config' #142
open the debug viewlet and click on 'configure launch config'.
Surprisingly, this takes a few seconds. Check the status line and see that the Java language server is starting
-> As I'm in a non-Java project, the Java debug extension should detect that and not try to contribute a debug configuration and start the Java language server
Because VSCode stopped supporting onDebug:type activation event, java debugger can only configure the activation event onDebug. It seems Java debugger/Language server extension will be activated so long as the user clicks F5 on any project.
Another scenario where this is problematic is if the user does not have a launch.json in their workspace.
For example: Create a new Express App and then press F5.
In this case, the debugger calls each installed extension which activates on onDebugInitialConfiguration. The Java Debugger was changed recently to activate onDebugInitialConfigurations (from onDebug) but in the non-launch.json scenario, the Java Debugger extension is activated and there is long delay without any status to the user while the Java Language Server is started.
Activity
testforstephen commentedon Nov 9, 2017
Because VSCode stopped supporting
onDebug:typeactivation event, java debugger can only configure the activation eventonDebug. It seems Java debugger/Language server extension will be activated so long as the user clicksF5on any project.gregvanl commentedon Jan 18, 2018
Another scenario where this is problematic is if the user does not have a launch.json in their workspace.
For example: Create a new Express App and then press F5.
In this case, the debugger calls each installed extension which activates on onDebugInitialConfiguration. The Java Debugger was changed recently to activate onDebugInitialConfigurations (from onDebug) but in the non-launch.json scenario, the Java Debugger extension is activated and there is long delay without any status to the user while the Java Language Server is started.
andxu commentedon Mar 5, 2018
DUP as #238, closing this one.