Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Correct way to initialize language server

See original GitHub issue

I am trying to initialize the language server using the below parameters but the ‘settings’ are ignored since the logs are the same even when the trace is changed, not sure if this is the correct approach to do so.

json.put("params", new JSONObject()
                .put("rootPath", path)
                .put("rootUri", "file:///" + path)
                .put("initializationOptions",
                        new JSONObject()
                                .put("settings", 
                                        new JSONObject().put("java", 
                                                new JSONObject()
                                                        .put("referenceCodeLens", 
                                                                new JSONObject().put("enabled", true))
                                                        .put("configuration", new JSONObject()
                                                                .put("updateBuildConfiguration", "automatic"))
                                                        .put("trace", new JSONObject()
                                                                 .put("server", "verbose"))))));

Thank you.

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

rgrunbercommented, Jun 3, 2021

Yeah, but I’ve got this after trying to attach Eclipse Debug Adapter Launcher to the language server:

Instead of “Eclipse Debug Adapter Launcher”, can you try using the “Remote Java Application” launcher ? It should be visible from debug configurations. In fact, if you have the JDT-LS launch folder also checked out in the workspace, you should see an option there called ‘jdt.ls.remote.launch’

0reactions

rgrunbercommented, Jun 29, 2021

Closing this, as it’s probably easier now to diagnose any issues when you’re able to debug the language server itself.