Breaking change in 9.3.0 regarding cross-project dependency manipulation #36428
Description
Current Behavior
- have a build with two projects
- put to the root project
subprojects { configurations.configureEach { allDependencies.configureEach { } } } - run
./gradlew dependencies
Ignoring that this is of course bad-practice cross-project configuration,
this works up to including 9.2.1 but fails with 9.3.0:
An exception occurred applying plugin request [id: 'org.gradle.java-library']
> Failed to apply plugin class 'org.gradle.api.plugins.JavaPlugin'.
> Could not create domain object 'java' (JvmSoftwareComponentInternal) in SoftwareComponent container
> Could not create domain object 'test' (JvmTestSuite) in TestSuite container
> Could not create an instance of type org.gradle.api.plugins.jvm.internal.DefaultJvmTestSuite.
> The value for property 'dependencies.compileOnly' property 'dependencies' is final and cannot be changed any further.
If that is an intentional new limitation, it should probably go through the usual deprecation cycle.
Expected Behavior
Not breaking in a minor update
Gradle version
9.3.0
Gradle version that used to work
9.2.1