The aim of this channel is to document the working practices of a half-decent software developer, so I pretty much show all the changes that I make to the source code of a project.
There is one exception to this convention; which is that I don’t subject you to the chores that are required to keep the build up to date. I upgrade versions, fiddle to make things faster, and sometimes even upgrade Gradle itself, all on my own time.
Today though I tried to modify the build of the JetBrains Ktor example project that we have been studying in recent videos (ktor.io/docs/server-create-ht.... I just wanted to get it to build and run on JDK 21, so that I could run benchmarks with Loom virtual threads.
I failed.
As failing to get Gradle to just do something is, in my experience, part of the working practices of a half-decent software developer, I’ve decided to make an exception to my exception and publish the attempt.
I’m probably missing something obvious. Maybe I just need to RTFM? No doubt there is a solution, but the sad fact is that where Gradle is concerned, even my 35 years of industry experience isn’t enough to keep me from stumbling around in the dark.
When you know how I'm being an idiot, you could fix things in github.com/dmcg/ktor-document... and let me know!
If you like this, you’ll probably like my book Java to Kotlin, A Refactoring Guidebook (java-to-kotlin.dev). It's about far more than just the syntax differences between the languages - it shows how to upgrade your thinking to a more functional style.
Негізгі бет Ғылым және технология We need to talk about Gradle
Пікірлер: 33