- Notifications
You must be signed in to change notification settings - Fork 245
Unify dependency versions #424
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
7d83ade to e7744b2 Compare build.gradle.kts Outdated
| // We could use a buildSrc script for this. | ||
| // See: https://github.com/gradle/kotlin-dsl-samples/issues/802 | ||
| plugins { | ||
| kotlin("jvm") version "1.8.10" |
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.
We are still hardcoding 1.8.10 here? Any way we can use the version from the platform project to avoid having this duplicate?
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.
Good point. It's not explicit in my initial revision but if you try to use another version that's different to what's constrained in the platform project, it'll complain stating the the lib is not found. I've refactored the plugins with their versions into a centralised place to live in settings.gradle.kts with a comment to make it obvious on how it all works. This will make it easier to see what versions we use.
gradle/platform/build.gradle.kts Outdated
| id("java-platform") | ||
| } | ||
| | ||
| group = "com.kotlin-language-server" |
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.
This should ideally match up with the package structure or at least an actual domain. Since the packages live in org.javacs.kt (as inherited by the original language server repo), we could use that with the disadvantage of it not being very descriptive.
As an alternative, I would propose
| group = "com.kotlin-language-server" | |
| group = "dev.fwcd.kotlin-language-server" |
Whether we would want to move the actual package structure to that too would be a topic for future debate.
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.
Sure thing, I've made the adjustment in my next revision!
e7744b2 to 05207f7 Compare | Thanks for the feedback, @fwcd and @themkat. I've pushed a squashed commit with the following changes:
|
| @RenFraser , if you rebase this branch with main, we can (probably) see that all the pipelines and Detekt are successful 🙂 Always good to check all of those going forward. (you would probably have to do it anyway because of the conflicts. Sorry for nagging, just my enthusiasm for seeing green builds with new stuff 😆 ) |
| Yeah, good idea. Let's resolve those conflicts and see all of our checks passing :) I'll rebase now |
Addresses fwcd#419
| Ok that looks good now @themkat :) |
| I say we merge this now, hopefully there isn't anything stupid we have missed this time 😆 Thank you @RenFraser ! 🙂 |
| Hm, I think this broke the |
Is that script even used anymore? Can't see it used in Github Actions |
| Yeah, it's meant for interactive usage |
We can probably get it working again by reading |
gradle.propertiesnow that we don't need to use it anymore.shared/build.gradle.ktsandserver/build.gradle.ktsfiles, the dependency declarations have just had their versions truncated.implementation("com.h2database:h2:1.4.200")becomesimplementation("com.h2database:h2"). Note the missing:1.4.200gradle.propertiesto the test additional workspaces since it's used during testing.gradle.propertiesto the test additional workspaces.