[ https://issues.redhat.com/browse/JBIDE-27119?page=com.atlassian.jira.plug... ] Martin Lippert commented on JBIDE-27119: ---------------------------------------- For the Spring Boot language server, we implemented an LSP4E-specific hover provider that can be registered as a hover provider in JDT. This is the registration piece: https://github.com/spring-projects/sts4/blob/master/eclipse-language-serv... Here is the implementation of the hover provider: https://github.com/spring-projects/sts4/blob/master/eclipse-language-serv... Since JDT doesn't combine the results from multiple hover providers, we had to take care of this ourselves, so that the regular Java hover would still appear in combination with ours for positions in the code where both hover provider could provide something. The additional requirement here is that you have to register your language server for the pre-defined Java source code content-type and make sure that it gets started when the Java editor opens. Would be more than happy to refactor and move this code (we have the same for content-assist) into LSP4E. Let me know if this approach would work for you, too, and we can start to contribute the code. -- This message was sent by Atlassian Jira (v7.13.8#713008)