Open cheonhyangzhang opened 4 years ago
Normally, navigation across multimodule gradle-based Java projects is expected to work except for Android, which is not supported. Since Scala is not supported by jdt.ls, navigating to scala source is not expected to work though. We have no plans on providing scala support in core jdt.ls. However, if someone wanted to add that as an eclipse.jdt.ls extension, we could provide some help (I can't guarantee it's doable, nor that it'll be easy)
Hi folks, I am trying to setup vim + coc java workflow for my work project. The project is a large java gralde project. It has many sub modules. Folder structure is like
When I load vim and JDT language server is running, all classes are working fine except the classes defined inside of /core module. The /core module is a little special because it needs scala cross build. (Not very familiar what does this actually mean)
In the settings.gradle file, it shows
I feel like when gradle builds the module, it renames the /core module into /core_2.11. So I am guessing probably due to the path name mismatch somewhere in language server to cause language server not able to recognize any class in /core module.
I am looking into the java language server eclipse.jdt.ls code to understand where this mismatch could be but so far didn't find anywhere yet. Actually not very familiar with how eclipse.jdt.ls is working.
Could anyone help me with a direction where should I look at? I feel when
typeDefinition
inNavigateToTypeDefinitionHandler.java
is called, it must look up somewhere. And this somewhere must be initialized with the location for every java class. I can't find where this initialization is.