Plugin incompatible with Gradle 9.0.0 for multi-module projects

[rkudryashov]

Describe the bug
The GraalVM native build tools plugin works correctly with Gradle 8.14.3 but fails with Gradle 9.0.0 in multi-module projects. The first module builds successfully, but the second module fails with configuration resolution errors.

To Reproduce

Clone https://github.com/rkudryashov/multi-module-native-repro
Build second module: ./gradlew :service2:bootBuildImage

Logs

```
./gradlew :service2:bootBuildImage                                                                                                                                                                                                                                       
> Task :service2:collectReachabilityMetadata FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':service2:collectReachabilityMetadata'.
> Failed to query the value of task ':service2:collectReachabilityMetadata' property 'metadataService'.
   > Could not isolate value org.graalvm.buildtools.gradle.internal.GraalVMReachabilityMetadataService$Params_Decorated@70dbf065 of type GraalVMReachabilityMetadataService.Params
      > Resolution of the configuration ':service1:detachedConfiguration9' was attempted without an exclusive lock. This is unsafe and not allowed.

* Try:
> For more information, please refer to https://docs.gradle.org/9.0.0/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors in the Gradle documentation.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to generate a Build Scan (Powered by Develocity).
> Get more help at https://help.gradle.org.

BUILD FAILED in 597ms
6 actionable tasks: 1 executed, 5 up-to-date

```

System Info (please complete the following information):

• OS: Windows
• Java Version: 24
• Plugin version: 0.11.0

[melix]

At this stage I suspect the issue is in fact in the Spring Boot plugin, I cannot reproduce without it.

[heruan]

I'm experiencing the same issue with:

OS: macOS
Java Version: 25 LTS
Plugin version: 0.11.0

We have this in the root project's build.gradle.kts:

plugins {
    alias(libs.plugins.graalvm) apply false
}
subprojects {
    if (gradle.startParameter.projectProperties.contains("native")) {
        apply(plugin = "org.graalvm.buildtools.native")
    }
}

to allow building native images with -Pnative e.g.

gradle :submodule:bootBuildImage -Pnative

[heruan]

At this stage I suspect the issue is in fact in the Spring Boot plugin, I cannot reproduce without it.

@melix have you been able to reproduce this with Spring Boot? I can provide a sample if that helps.

[melix]

No, but I think this belongs to the Spring Boot repository, not this one.

[rkudryashov]

The issue is not reproduced after upgrade to Spring Boot 4.0.0-M3, so that seems the easiest way to fix the issue

[wilkinsona]

That's not what I described in spring-projects/spring-boot#47308. The issue occurs with Spring Boot 4.0.0-M3 and, perhaps more importantly, without Spring Boot at all.

[heruan]

The issue is not reproduced after upgrade to Spring Boot 4.0.0-M3, so that seems the easiest way to fix the issue

As also @wilkinsona reported, I confirm the issue does still happen with Spring Boot 4.0.0-M3 on an intermittent basis.

Could not isolate value org.graalvm.buildtools.gradle.internal.GraalVMReachabilityMetadataService$Params_Decorated@70dbf065 of type GraalVMReachabilityMetadataService.Params

This sounds like the native-build-tool plugin is trying to do something that Gradle 9 does not like, that maybe was permitted before?

[rkudryashov]

I only described how the repro-project can be fixed

[wilkinsona]

It doesn't fix it. The problem occurs with Spring Boot 4.0.0-M3 and, indeed, without any version of Spring Boot's Gradle plugin.

[rkudryashov]

ok, I'll clarify what I meant: upgrading Spring Boot's version from 3.x.x to 4.0.0-M3 in the repro-project (here) fixes the error I initially reported in this thread

[rkudryashov]

I don't know why but after upgrade and several builds I don't see the reported error. Maybe that's just my environment, and on other ones the issue is still reproduced