It’s little bit off-top probably. But is it look s...

# gradle

[gildor]

It’s little bit off-top probably.
But is it look strange only for me that kotlin-dsl provides shortcut that specific only for Kotlin project (kotlin() or kotlinModule() before)?

kotlin(“…”) method in kotlin-dsl is really convenient but forces you to use wrong approach, because your project implicitly relates now on version of Kotlin bundled to kotlin-dsl this approach doesn’t look like recommended way to configure you project.
Of course you can specify version explicitly, but I think most developers don’t do that.

if you use kotlin-gradle-plugin with new plugins dsl you can omit version as well and you always want to use same version of plugin with same version of other kotlin dependendencies.
Maybe better to move kotlin(“module”) extension to kotlin-gradle-plugin to allow use it. Looks like much better way to help configure project, actually it’s just additional helper function in plugin-specific DSL.

I thought that Gradle is not biased to any specific project type and I think it’s a good thing and kotlin-dsl should follow this strategy.

P.S. I very like idea of helper methods for project to reduce copy-paste of dependency ids and boiler plate extraction of dependency versions.
I would really want such thing in Android plugin for support-library dependencies. But it should be a part of plugin, not Gradle or kotlin-dsl API