Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
eclipse.jdt.ls can retrieve definitions for symbols located in jar files.
Example:
In a maven project, when cursor is on
JMSExc|eption
, :LspDefinition would reply with the following, including exact source file name and line/column location:The
"uri"
string contains the location of the jar file, and within it the full of theJMSException.java
file.This patch converts this
"uri"
string into the following:The
zipfile://<path>.jar::<path>
format is understood by vim and therefore it can open the definition.Note that this is tested with a maven project, after
dependency:sources
downloaded the-sources.jar
files for the otherwise binary dependencies.Now this is clearly a proof-of-concept and not something I'd consider to be merged. However it worksforme and would be nice if vim-lsp's
s:lsp_location_item_to_vim
function could handle othe "proprietary" URI specifiers, includingjdt://
.