Closed takadev15 closed 1 year ago
Running :JdtCompile
should show some more details if it can't build the project. See also the troubleshooting section.
Given that the other project works, this doesn't seem to be a client issue, but might be a server/gradle integration issue in which case you'll have to report this upstream in the eclipse.jdt.ls repo. (You could double check if you can get it working with the vscode java extension for good measure)
LSP client configuration
Here's my nvim-jdtls configurations
Eclipse.jdt.ls version
No response
Steps to Reproduce
The problems only appear on my work java's project. I already tested this plugin on other file with similar file structure with my workfile (https://github.com/FabricMC/fabric) and it works perfectly.
i'm suspecting the problem lies on dependecies on my works java project. Since one of the dependencies used is a my company specific private registry. even tough i already specified the keys in local.properties on root project i suspected this information isn't used by jdtls.
Expected Result
lsp.log for success lsp attaching (fabric project)
Actual Result
lsp.log for when i started jdtls on work's project
and after starting diagnostic on file showing