-
|
Found some projects that might be helpful https://github.com/uzxmx/coc-java-dependency and https://github.com/Microsoft/vscode-java-dependency. The latter one is a jdtls extension, and hopefully we can just plug it into nvim-java Edit : Other related projects that might also be helpful https://github.com/microsoft/vscode-gradle & https://github.com/Microsoft/vscode-maven. I couldn't see specific classes/files being accessed through these, but be helpful for implementation or something |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
{{title}}
Uh oh!
There was an error while loading. Please reload this page.
-
(This might be out of scope for this plugin specifically)
I often find myself looking through classes and file structure of my dependencies to look at the API or figure out how specific things are done in provided examples and library classes (sources). It would be really helpful if there was a way to look at all dependencies/libraries at a glance and traverse through them in some kind of tree (maybe even an extension to neo-tree).
How do you tackle such a situation? Could we have a system in place for nvim-java to look through the jars? Or should a generalized approach through plugin is the way to go ?
Beta Was this translation helpful? Give feedback.