-
-
Notifications
You must be signed in to change notification settings - Fork 9
Add initial gradle support #1
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
Conversation
As a note, this branch might be idle for about a week, was just excited to see this project @amgdev9 so took a stab at it right before I'm leaving for holiday 😅. |
Hi @samneirinck! Thanks for your PR 😄
For now just pass it as an argument, when this grows we'll see to refactor the gradle resolver into a class or context receiver
Right now JDK dependency is not working in the LSP, I'm currently working on it and just today I got imports to be resolved correctly, but there are some services to implement to get rid of all the error diagnostics. Step by step 🚀
No worries! Take your time, there is still plenty to do, this project is just starting |
Does this LSP aim to target Kotlin with the full Multiplatform targets, or just the JVM part? |
Right now I am focusing on jvm support, but the rest of the targets we can provide support for them as well in the future no problem |
Nice, thanks. I have asked because K/M support is a must have (imo) for Kotlin's usability. |
20e3e90
to
fa61c9b
Compare
Rebased on the latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, thank you so much for your contribution!
fa61c9b
to
cdaa09a
Compare
Adds initial support for Gradle via Gradle Tooling.
It does so by implementing the
GradleBuildSystem
class, letting Gradle Tooling resolve all modules/dependencies, and then map those to the correctLibraryModule
andSourceModule
s.Verified this locally on neovim with no additional configuration required.