A modern programming language that makes developers happier.

kotlinlang

Is there a way to get Gradle's Kotlin DSL to autogenerate type-safe accessors for items in the `gradle.properties` file like it used to for Groovy?  Instead of having to bind every single one manually with `val foo by properties`.

Not by default. You could write such generator by yourself, but I would recommend convention plugins instead. 

Groovy is also not type safe, but supports dynamic „typing“. 

How do you make convention plugins work there? Variables don't carry over between scripts, even if you `include` them

Oh I bet you can do `val Project.foo by properties` , can't you

If you need to apply the same logic in different projects, just apply the convention plugin in each project

I mean this:
```// buildSrc/.../my.convention.gradle.kts
val myProperty = "foo"

// build.gradle.kts
plugins {
  id("my-convention")
}

println(myProperty) // can't reference it```

I want to have constants that are used in multiple places bound in one place

like my project coordinates, url, other metadata

You can have constants in a kt file in build-logic

multiple convention plugins will use the information, but the constants should be in one place

&gt; You can have constants in a kt file in build-logic
Could you explain? I've never been able to get that to work.

Do you mean just a plain ol kotlin file, not .gradle.kts?

<https://github.com/hfhbd/ComposeTodo/blob/main/gradle/build-logic/src/main/kotlin/AndroidConfigs.kt#L32|https://github.com/hfhbd/ComposeTodo/blob/main/gradle/build-logic/src/main/kotlin/AndroidConfigs.kt#L32>

I wasn't aware those got resolved. Neat, thanks!

Do you need to do anything to import them into a script like with convention plugins? Or are they automatically brought into all buildscripts in the project?

It depends. Inside your build-logic src, it is a variable/function/getter, so you need to import it like regular kotlin, eg packages etc. 

But I mean they're just on the gradle file's classpath by default?

If you also want to use it from your actual projects, you need to include the build-logic classes in your project classpath, and the easiest way to do this is using a settings plugin

Like I did here <https://github.com/hfhbd/ComposeTodo/blob/main/settings.gradle.kts#L11|https://github.com/hfhbd/ComposeTodo/blob/main/settings.gradle.kts#L11>

Wow yeah ok, I had no idea buildSrc allowed regular kotlin files

If it is in `buildSrc` it is in an ancestry classloader of all project build scripts, so like the plugins available everywhere.

If it is in a proper included build, it is only available where you use it and thus does not invalidate everything unrelated, meaning, if you apply a plugin from the same project the class is available, or if you declare a buildscript classpath dependency.
Or if it is in an ancestry classloader like the settings script classloader.

Btw. "project coordinates" sounds like a bad idea, at least if you use it to manipulate a publication, that is seldomly a good idea and you should instead make the defaults work, or you for example need manual substitutions as soon as you want to use the build in a composite build and so on.