so the whole daemon-jvm thing doesn't work out of the box?

./gradlew updateDaemonJvm --jvm-version=21

Configuration cache state could not be cached: field `__toolchainDownloadUrls__` of task `:updateDaemonJvm` of type `org.gradle.buildconfiguration.tasks.UpdateDaemonJvm`: error writing value of type 'org.gradle.api.internal.provider.DefaultMapProperty'

There is a prominent warning in the docs of the feature saying

This process requires toolchain download repositories to be configured. See below for details.

yes, but... that's awful 😕 seems like yet another unfinished feature

Of course, it is still incubating

lol

First thing in the docs

is version catalog still incubating?

If you have thoughts, share them with the Gradle folks, now is the time to do even breaking changes lightly

seems like an unfinished feature

Not to me

really? oh right, you don't use buildSrc

I use included build for build logic not

buildSrc

. But if this is about not having type-safe accessors, well that is by design of how the feature works and there are work-around for those wanting to still do it under some restrictions. So not really a sign for the feature not being finished, more that you are not happy with the design decisions done.

different definitons of done... consistent apis is done 😉

What is not consistent?

how I add things to any given dependency block

Well, things evolve and need to transition without breaking everyone's builds

never ever breaking api/abi is not a great idea (so sayeth our completely broken gradle setup at work )

Please don't speak for all people, but just yourself, because you reflect my opinion in practically 0 way. If you have thoughts about the backwards compatibility policy, direct them to the Gradle folks. But I hope that they will not consider and also think they will not, because it is breaking enough already and also many users complain that it evolves too quickly for their taste, not too fast. Also if your build is that badly broken, it is most likely not the fault of Gradle. 😉

if gradle disallowed things it now considers bad 😉

Yes, that would break people's build and make them upset and rightfully so

I'm saying that they should break more things with major versions... like most of this stuff hasn't been a good idea for something like 10 years