Gradle extension plugin's `validateExtension` incompatible with Gradle 9

[ryandens]

Describe the bug

First reported here but was waiting to extract a reproducer to file a full report

The validateExtension task produces deprecation warnings on Gradle 8.14.3 and fails on Gradle 9.0.0-rc-3 when running with org.gradle.parallel is set to true.

The deprecation warning is

Resolution of the configuration :example-deployment:runtimeClasspath was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behavior has been deprecated.

The quarkus validateExtension task resolves the deployment runtime classpath here

This happens without declaring an explicit dependency on the project as would traditionally be recommended (see https://docs.gradle.org/8.14.3/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors)

This is done in this unconventional way to work around Gradle's protections against circular dependencies (where the deployment module depends on the extension module and the extension module consumes the deployment runtime classpath).

Expected behavior

Can run Gradle build without deprecation warnings in preparation for Gradle 9 as described in #48524

Actual behavior

This deprecation warning appears when building an extension in a build that sets org.gradle.parallel to true, which is why it was not detected during the initial validation of Gradle 9 with Quarkus.

This is intended behavior of Gradle in Gradle 9: gradle/gradle#33938

How to Reproduce?

1. Clone https://github.com/ryandens/quarkus-extension-gradle-reproducer
2. ./gradlew build

Build scans
Gradle 8.14.3: https://scans.gradle.com/s/ispyasboxlgy2/deprecations
Gradle 9.0.0-rc-3: https://scans.gradle.com/s/4uad4owi7xpe6

Output of uname -a or ver

No response

Output of java -version

OpenJDK Runtime Environment Temurin-21.0.6+7

Quarkus version or git rev

3.25.0

Build tool (ie. output of mvnw --version or gradlew --version)

Gradle 8.14.3 / Gradle 9.0.0-rc-3

Additional information

No response

[quarkus-bot]

/cc @glefloch, @quarkusio/devtools

[siddharthapd]

Hi Do we know by when this will be solved ?
Most of the extension projects are not compatible with old style gradle compileClasspath and validateExtension. Currently i am using prop validateExtension.enabled=false in runtile module in order to process, but for some projects where ./gradlew sonar is called, i am getting

g:
Execution failed for task ':sonar'.
> Resolution of the configuration ':runtime:compileClasspath' 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.

[mschorsch]

We have the same problem with Sonar.

Cc @aloubyansky

[mschorsch]

@siddharthapd As a workaround you can execute gradlew sonar --no-parallel.

[siddharthapd]

Thank you @mschorsch . Yea i am aware of that, but that reduces the pipeline efficiency.

Hopeful we get fix in 3.26.4 onwards.

[gwitsch]

Having the same issue with Gradle 9.0.0. and 9.1.0
By the way, Gradle does already warn about the problem in Gradle 8.14.3

gradle compileTestJava --rerun-tasks --warning-mode all

> Task :shareLoggerExtension:validateExtension
Invocation of Task.project at execution time has been deprecated. This will fail with an error in Gradle 10.0. This API is incompatible with the configuration cache, which will become the only mode supported by Gradle in a future release. Consult the upgrading guide for further information: https://docs.gradle.org/8.14.3/userguide/upgrading_version_7.html#task_project
Resolution of the configuration :shareLoggerExtension-deployment:runtimeClasspath was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behavior has been deprecated. This will fail with an error in Gradle 9.0. For more information, please refer to https://docs.gradle.org/8.14.3/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors in the Gradle documentation.

I first assumed that my problem is caused by changing the sub-projects' names in the settings.gradle file from the plugin parent.

project(':deployment').name = 'shareLoggerExtension-deployment'
project(':runtime').name = 'shareLoggerExtension'

But i am not sure if this is really the problem. Did not yet try to create a dummy plugin following the guide.

Just did a small test with the help of Copilot. Changing my subprojects' names by using another API does not solve the problem.
However, running the build single threaded fixes the problem for now.

gradle clean compileTestJava --rerun-tasks --no-parallel

But there is still a warning not to be ignored:

gradle compileTestJava --rerun-tasks --no-parallel --warning-mode all

> Task :shareLoggerExtension:validateExtension
Invocation of Task.project at execution time has been deprecated. This will fail with an error in Gradle 10. This API is incompatible with the configuration cache, which will become the only mode supported by Gradle in a future release. Consult the upgrading guide for further information: https://docs.gradle.org/9.1.0/userguide/upgrading_version_7.html#task_project