Yeah, the overall idea is that
org.eclipse.lsp4e.jdt
provides the implementation for the Java completion proposal computer FOR ALL available language servers. So if you have a language server that provides completion support for Java source files, all you need to do is to include the org.eclipse.lsp4e.jdt bundle instead of implementing your own completion proposal computer (and, of course, associate your language server with the Java source file content type).
Cheers Martin
Found the cause: seems the camel tooling has an IJavaCompletionProposalComputer that is duplicating the LSP4E JDT one.
I started and I can see that 2 providers are returning items to org.eclipse.jdt.internal.ui.text.java.ContentAssisProcessor so the list is of size 4 and not 2. The list is supposed to be filtered and sorted but it does not seems to be implemented Need to determine why 2 providers are used
--
-- _______________________________________________lsp4e-dev mailing listlsp4e-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/lsp4e-dev
|