This message was deleted.

Most of the time its dependencies, compiler/linker flags. However, in our case, we are moving away from simple string/integer in favour of more complete objects that user can define to account for missing modelling from our plugins.

We are going to introduce some form of declarative files as an alternative to the existing DSLs. There's some detail in the blog post: https://blog.gradle.org/declarative-gradle

If the idea is to go with what Amper did, I’m not sold to that idea. I understand the idea to make it more easy to parse using tools but I believe it’s possible to achieve using an subset of the common syntax between Groovy and Kotlin DSL. The up-most best would be declarative DSL would be full compatible as Groovy or Kotlin DSL but easy to parse given the strict and narrow syntax support. Bazel is somewhat doing that, starlark being a subset of Python. We could have Gradle DSL which would be a subset of Groovy/Kotlin DSL. That would be super cool (as opposed to Amper direction).

That's exactly the plan. We're experimenting with a strict subset of Kotlin, and a way of exposing the models so that you can use the same syntax in both the Kotlin DSL and the declarative files.

I’m glad to learn my assumption was correct. It reduce my anxiety on that subject. 😉