A modern programming language that makes developers happier.

kotlinlang

<https://github.com/JetBrains/kotlin-examples/pull/60>

I don't think we should mix together Gradle Kotlin DSL and DCE example.

I mean, most newcomers are probably familiar with Groovy syntax, but unfamiliar with Gradle Kotlin DSL

And most of people who get to this example, get there from DCE article in <http://kotlinlang.org|kotlinlang.org>. They need to learn how to use DCE, not how to use Kotlin DSL

As you want, I will publish shortly this as part of a distinct example

I hope you will migrate examples to Gradle Kotlin DSL asap they release a usable documentation

Also KT-20156 need to be fixed to make that usable in real life

Is there any blocking issue that prevent publishing the JS and DCE plugin to Gradle portal ? Or is it "just" in your long todo list ?

I don't know. I'm not responsible for Gradle plugins

Since most of the core Kotlin code base has recently switched from traditional Gradle DSL to Gradle Kotlin DSL this is becoming a *BIG* issue! Looking at the Kotlin JS Code base for example, almost all of it uses the Gradle Kotlin DSL. Even Kotlin JS DCE uses it (<https://github.com/JetBrains/kotlin/blob/master/js/js.dce/build.gradle.kts>).

I don't understand why the DCE plugin isn't compatible with Gradle Kotlin DSL when using the plugin, yet the plugin *depends* on Gradle Kotlin DSL in order to be built. :confused:

<@U5R5FGVH7> that's not an issue at all. We build JS and JS DCE using Kotlin DSL, but we don't use either JS or JS DCE plugins during build. So what's the problem?

The problem is that the plugins *should* have been made usable when a user wants to use them via Gradle Kotlin DSL. Currently the plugins are designed for use by the traditional Gradle DSL, and it appears no work has been done to ensure the plugins work with Gradle Kotlin DSL. All Kotlin JVM plugin(s) for instance work fine with Gradle Kotlin DSL, and there should be no reason why the Kotlin JS plugins cannot work as well.