Open bitspittle opened 5 months ago
Yes this can be done using the gradle tooling api. Probably by either making the kobweb gradle plugin build a model, or what i have seen the kotlin gradle plugin doing, injecting custom code when running gradle from the tooling api
Actually i think just implementing this in the gradle plugin and logging a warning is the proper solution
Not a bad thought! Two possible problems I see with the Gradle approach:
If we use the IDE to detect this, we can show a message via a notification bubble that's 1) really easy to see and 2) includes a link that the user clicks on which could just fix this for them.
BTW, it's possible we should do both things. The Gradle plugin should list a warning, AND the IDE should have integrations for detecting and helping with it.
Fair. We can log a warning and add some version mismatch info to the Gradle model. Will probably start working on the model tomorrow
Can we discover those versions from the project's Gradle model? Worst case, we can parse
libs.versions.toml
directly, but that's more fragile. What if a user isn't using version catalogs?