build(deps): bump dev.gradleplugins.groovy-gradle-plugin from 1.7.1 to 1.9.0

[dependabot]

Bumps dev.gradleplugins.groovy-gradle-plugin from 1.7.1 to 1.9.0.

Release notes

Sourced from dev.gradleplugins.groovy-gradle-plugin's releases.

v1.9.0

This release improves the gradlePlugin extension by introducing a new dependencies feature. This simplifies the declaration of dependencies by organizing them into declarable buckets, enhancing support for version catalogues and improving code completion. Additionally, test suites received significant improvements.

The gradlePlugin.dependencies extension is designed to clarify intent compared to using project.dependencies. Configuring implementation dependencies with the project DependencyHandler targets the main source set, which may be misleading if developers configure the gradlePlugin.pluginSourceSet. We maintain clear intentions by deferring dependencies configuration until pluginSourceSet is finalized thanks to the dependencies extension. Future versions will assert consistency if pluginSourceSet changes unexpectedly.

Additionally, new dependency types for plugin authors allow easier and more stable dependencies on other plugins. Instead of knowing a plugin's Maven coordinates, you can now use gradlePlugin('<plugin-id>:<version>'), which returns an ExternalModuleDependency to the plugin JAR:

gradlePlugin {
    dependencies {
        implementation(gradlePlugin("com.example.my-plugin:4.2"))
    }
}
dependencies {
compileOnly(gradlePlugin("com.example.my-plugin:4.2"))
}

v1.8.0

This release introduces the capability to distinguish the plugin API and implementation. The distinction can be made using two jar tasks or source sets. The following example shows a glance of what this new capability is about:

// Remove `api` packages from implementation JAR
tasks.named('jar', Jar) {
    exclude('**\/api\/**')
}
// Configure Gradle plugin API as a custom JAR that only include api packages

gradlePlugin {

api {

jarTask = tasks.register('apiJar', Jar) {

from(sourceSet.flatMap { it.output.elements })

include('/api/')

archiveClassifier = 'api'

}

}

}

Note this feature may receive breaking changes over the next few releases. Feel free to give it a try and report any issue you encounter.

v1.7.2

This release fixes an issue introduced in version 1.7.1 regarding the declaration of dependencies on test suites.

Commits

• 8c96a78 Use special hamcrest matcher for Gradle property non-mutable exception
• 87ff151 Prepare v1.9.0
• 111a99e Update compatibility for Gradle 8.9
• 1b5e206 Merge pull request #106 from gradle-plugins/develop/dependencies
• a5fe9b6 Remove reliance on Groovy code for Groovy DSL decoration
• b296ba1 Improve supports for minimum Gradle support and custom plugin source set
• fd213dd Fix some assertions
• 0e39338 Fix decoration of DependencyHandler and RepositoryHandler
• 2bf1828 Fix test failures
• 3828ae8 Prepare 2.0 TODOs
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)