In previous samples, there was always the gradle p...
# multiplatform
d
In previous samples, there was always the gradle plugin specified as classpath, in the project’s gradle file, as a dependency of the buildscript
Copy code
buildscript {
    repositories {
        gradlePluginPortal()
        google()
        mavenCentral()
    }
    dependencies {
        classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:${kotlin.version}")
    }
}
But in the latest multiplatform samples, the buildscript section is not included anymore. Does buildscript belong to an old way of configuring gradle, or is it still relevant today? Previously, the documentation of popular libraries such as Kotlin Serialization or SqlDelight required to have a classpath specified as a dependency of buildscript, but now not anymore.
f
You can add them as aliases now i believe