From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Hi all. Was hoping for a sanity check on this approach because I feel like it may break the configuration cache but I'm not sure. The core of my question is, is it safe to store a lambda in a shared build service (configured in the root build.gradle.kts) that is then used by convention plugins later on? Example in the :thread:

So in my root build.gradle.kts I have:
```yum {
    loggingConfiguration { 
        dependencies {
            "implementation"(projects.logging)
            "testImplementation"(libs.slf4j.simple)
        }
    }
}```
The root convention plugin method looks like:
``` fun loggingConfiguration(action: Project.() -&gt; Unit) {
        YumGlobalConfigService.of(project).get().loggingConfiguration = action
 }```
Then each child project's extension calls the following method when I enable logging
```private fun Project.addLoggingSupport() {
    val service = YumGlobalConfigService.of(this).get() 
    service.loggingConfiguration(this)
}```
Important to note that `YumGlobalConfigService.of` is a shared build service
```fun of(project: Project): Provider&lt;YumGlobalConfigService&gt; {
            return project.gradle
                .sharedServices
                .registerIfAbsent(
                    "YumGlobalConfigService",
                    YumGlobalConfigService::class.java
                ) {
                    /* do no config */
                }
        }```
