v1.6.0
This release contains mostly refactorings, to enable some of the enhancements planned for the future.
Most notably, the project structure has been split up into a multi-module build, and helm-publish
and helm-releases
plugins are now kept in their own subprojects. This also avoids fetching unnecessary dependencies (e.g. a HTTP client when publishing is not used). These plugins are now delivered as separate JAR artifacts from the plugin portal.
As a consequence, it might be necessary to explicitly add the version to each of the plugins, especially when the single-library JAR was imported using an apply false
statement before.
If you have this in your root project:
plugins {
id("org.unbroken-dome.helm") version "1.5.0" apply false
}
Then subprojects can no longer automatically use the org.unbroken-dome.helm-publish
and org.unbroken-dome.helm-releases
plugins because they now reside in separate JARs. You will need to declare them as well:
plugins {
id("org.unbroken-dome.helm") version "1.6.0" apply false
id("org.unbroken-dome.helm-publish") version "1.6.0" apply false
id("org.unbroken-dome.helm-releases") version "1.6.0" apply false
}
Alternatively, you can use the following snippet at the beginning of your settings.gradle or settings.gradle.kts, to keep the version in a single place. This will then allow you to omit the version whenever you declare the plugin in a build.gradle(.kts) file.
pluginManagement {
resolutionStrategy.eachPlugin {
if (requested.id.namespace == "org.unbroken-dome" && requested.id.name.startsWith("helm")) {
useVersion("1.6")
}
}
}