-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ImplementationProvider Support #556
Comments
The lsp4j will need to be updated to reflect the new specification. |
Filed eclipse-lsp4j/lsp4j#178 for LSP4J |
17 tasks
fbricon
added a commit
to fbricon/eclipse.jdt.ls
that referenced
this issue
Aug 25, 2018
java.lang.Object is treated as a special case. Because of its large type hierarchy, implementation location is not computed from reading all files. Instead a default location at 0,0 will always be returned. Fixes eclipse-jdtls#556 Signed-off-by: Fred Bricon <fbricon@gmail.com>
fbricon
added a commit
that referenced
this issue
Aug 27, 2018
java.lang.Object is treated as a special case. Because of its large type hierarchy, implementation location is not computed from reading all files. Instead a default location at 0,0 will always be returned. Fixes #556 Signed-off-by: Fred Bricon <fbricon@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See microsoft/language-server-protocol#156
and redhat-developer/vscode-java#446
The protocol has not been updated yet. We need to add a protocol extension (in lsp4j?)
The text was updated successfully, but these errors were encountered: