buildInfo does not work with Gradle 8.7 or later when the configuration cache is enabled about spring-boot HOT 4 CLOSED

I just tested that as a workaround, you can add this line to your gradle.properties:

org.gradle.jvmargs=--add-opens java.base/java.util.concurrent.locks=ALL-UNNAMED

from spring-boot.

Seeing the same problem with Boot 3.2.6 and 3.3.0. Earlier versions do not have this issue.
This seems to come down to BuildInfoProperties using the SingletonSupplier of springframework.spring-core. Boot 3.2.5 comes with Spring Framework 6.1.6 where the SingletonSupplier does not have the writeLock field. Boot 3.2.6 and 3.3.0 use Spring Framework 6.1.8 where the afformentioned field exists in SingletonSupplier

Removing the buildInfo configuration or disabling the configuration cache is currently a workaround for us, but not really an optimal solution

EDIT: Boot 3.2.5 comes with Spring Framework 6.1.6 where SingletonSupplier.writeLock exists, however spring-boot-gradle-plugin:3.2.5 comes with springframework.spring-core:6.0.10 where SingletonSupplier.writeLock does not exist

from spring-boot.

I think it should be handled at Gradle side.

from spring-boot.

Thanks, @jkuipers, and apologies for the regression. This is an unanticipated side-effect of #40074. You can also work around the problem by using Gradle 8.6 or earlier.

from spring-boot.