Closed SimonMarquis closed 5 months ago
There is one last thing to do, which is to update the "Adding to the Buildscript Classpath".
To me, there is no point of adding the plugin to the classpath this way since we already show how to add it with:
plugins {
id("com.dropbox.dependency-guard") version "..."
}
Or is it used for something else I did not thought about?
The Legacy Plugin API using the buildscript block feels outdated and is probably no longer used for people wanting to test the snapshot versions.
Could we replace it with something like this?
Snapshot versions are under development and change, but can be used by adding in the snapshot repository
// settings.gradle.kts
pluginManagement {
repositories {
maven { url = uri("https://s01.oss.sonatype.org/content/repositories/snapshots") }
}
}
// build.gradle.kts
plugins {
id("com.dropbox.dependency-guard") version "x.y.z-SNAPSHOT"
}
This also migrates the 2 remaing Groovy Gradle build files to kts.