I think you needed to just specify a version next to `kotlin("jvm")` so that it can pull the right one. I think that's likely better than the "old Gradle" buildscript approach
Thank you, let me try that. On reflection, I think that my major problem is the mental model behind a Gradle build is a moving target. For a new build, tools can generate something that just works, requiring no understanding. Where I need more sophistication I can gain the knowledge it when I need it. But the combination of other people’s builds and changing Gradle models can reveal huge gaps in my knowledge and models for a conceptually simple change.
Thank you, I’ll give that a go. It seems to me that the number of times I want non-latest versions of the actual build tools is pretty much zero, with the exception of Gradle, that keeps on depreciating things.
I think you needed to just specify a version next to `kotlin("jvm")` so that it can pull the right one. I think that's likely better than the "old Gradle" buildscript approach
Thank you, let me try that.
On reflection, I think that my major problem is the mental model behind a Gradle build is a moving target. For a new build, tools can generate something that just works, requiring no understanding. Where I need more sophistication I can gain the knowledge it when I need it. But the combination of other people’s builds and changing Gradle models can reveal huge gaps in my knowledge and models for a conceptually simple change.
I think you can specify the Kotlin version as "latest.release" or "+" to avoid setting a specific version.
Thank you, I’ll give that a go. It seems to me that the number of times I want non-latest versions of the actual build tools is pretty much zero, with the exception of Gradle, that keeps on depreciating things.