Java: helix can find documentation but cannot go to implementation

[AdityaMayukhSom]

Summary

I was implementing an XML syntax checker in java, when I required to see the inner implementation of a class implemented in core java. But when I used gd it showed no definition found.

But when using Space-k, it can fetch the documentation and show it. I am using jdtls as the language server.

I tried gd on a locally implemented class and it worked fine by opening the declaration of the class in a new buffer.

I tried with classes imported from packages installed by maven, but there too the documentation was fetched but the class definition could not be opened.

Reproduction Steps

I tried this:

1. Opening a java file in helix.
2. Importing a class from core java.
3. Invoked gd on the class name.

I expected this to happen:

The class definition to get opened in a new buffer.

Instead, this happened:

no definition found was showed in the status line.

Helix log

~/.cache/helix/helix.log

2023-12-12T00:44:53.404 helix_lsp::transport [ERROR] jdtls err <- "WARNING: Using incubator modules: jdk.incubator.vector\n"
2023-12-12T00:44:54.356 helix_lsp::transport [ERROR] jdtls err <- "Dec 12, 2023 12:44:54 AM org.apache.aries.spifly.BaseActivator log\n"
2023-12-12T00:44:54.356 helix_lsp::transport [ERROR] jdtls err <- "INFO: Registered provider ch.qos.logback.classic.servlet.LogbackServletContainerInitializer of service jakarta.servlet.ServletContainerInitializer in bundle ch.qos.logback.classic\n"
2023-12-12T00:44:54.361 helix_lsp::transport [ERROR] jdtls err <- "Dec 12, 2023 12:44:54 AM org.apache.aries.spifly.BaseActivator log\n"
2023-12-12T00:44:54.361 helix_lsp::transport [ERROR] jdtls err <- "INFO: Registered provider ch.qos.logback.classic.spi.LogbackServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle ch.qos.logback.classic\n"
2023-12-12T00:44:57.066 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2023-12-12T00:44:57.068 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2023-12-12T00:44:58.334 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2023-12-12T00:44:58.881 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2023-12-12T00:44:58.971 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2023-12-12T00:44:58.972 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2023-12-12T00:44:58.973 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2023-12-12T00:44:59.014 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2023-12-12T00:44:59.030 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2023-12-12T00:44:59.030 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled

Platform

Linux

Terminal Emulator

xterm-256color

Installation Method

zypper

Helix Version

helix 23.10 (f6021dd)

[TornaxO7]

According to the nvim-lspconfig repository you need an extension to do that: neovim/nvim-lspconfig#784 (comment)

[TornaxO7]

And if I'm seeing that correctly this would have to be implemented in helix.

[AdityaMayukhSom]

According to the nvim-lspconfig repository you need an extension to do that: neovim/nvim-lspconfig#784 (comment)

As helix currently does not support any extensions, are there any workarounds for now to this problem? As sometimes there are virtually no documentation and inspecting the inner implementations of the class is the easiest way to understand it's purpose.

[TornaxO7]

Hm... I think a PR which implements the extensions might be the solution for this but maybe there's another way which I'm not aware of.

[gabydd]

We don't support non standard lsp extensions in core(that would be a constant cat and mouse) so this would have to either be in a plugin or implemented without and extension in jdtls

[TornaxO7]

this sounds reasonable