I got this at the moment, but that doesn’t work: `...

# announcements

[hellman]

I got this at the moment, but that doesn’t work:

plugins {
    id("org.jetbrains.kotlin.js") version "1.3.60-eap-76"
}

repositories {
    mavenCentral()
    mavenLocal()
    maven(url = "<https://dl.bintray.com/kotlin/kotlin-eap>")
}

[oskarh]

I haven’t tried out EAP myself but according to the pinned message in #C0KLZSCHF you can follow the instructions at https://discuss.kotlinlang.org/t/kotlin-1-3-60-early-access-preview/14579

[hellman]

Can’t get it to work with a Kotlin gradle script. 😕

[hellman]

It works if I use regular gradle script,

[oskarh]

Don’t have much experience with kotlin gradle scipting either I’m afraid. Maybe someone in #C19FD9681 can help you out?

[Mike]

Plugins don't use the same repositories as the one listed there. It's a bit confusing at first. The Build script has it's dependencies/configuration, and your actual build has its.

In settings.gradle, add

pluginManagement {
    repositories {
        maven(url = "<https://dl.bintray.com/kotlin/kotlin-eap>")
    }
}

Although that's acceptable for Groovy so may have to tweak a bit for Kotlin DSL.

[Mike]

It was clearer when they used the buildscript block, but also more clutter in your main build file.

[hellman]

wait, so with Kotlin Gradle script you don’t use buildscript anymore?

[hellman]

Also, why settings.gradle? Why can’t I put that in build.gradle.kts?

[Mike]

No, it's not Kotlin Gradle that changed this. You have 2 ways to bring plugins into your build.

Either with buildscript OR using the plugins block. The plugins block is the recommended approach now. It can speed up build configuration phase BUT does have some syntax restrictions as a result. Won't go into details here.

If you use buildscript, then everything is in the build.gradle file.

If you use plugins, then plugin configuration goes into the settings file.

[Mike]

https://docs.gradle.org/current/userguide/plugins.html#sec:plugins_block

[Mike]

If you go to the end of the Limitations of the plugins DSL section, you'll see this

If the restrictions of the plugins {} block are prohibitive, the recommended approach is to apply plugins using the buildscript {} block