You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ForceDependencyResolutionPlugin incompatible with Project isolation #109
The plugin ForceDependencyResolutionPlugin isn't compatible with upcoming project isolation because it registers a root task depending on sub-project tasks.
Instead, a settings plugin should add an outgoing configuration by applying a project plugin to each subproject and add a root plugin consuming the configurations.
Failing output using Gradle 8.6 (or 8.7-20240205001347+0000)
- Plugin class 'org.gradle.forceresolve.ForceDependencyResolutionPlugin': Cannot access project ':day1' from project ':'
- Plugin class 'org.gradle.forceresolve.ForceDependencyResolutionPlugin': Cannot access project ':day2' from project ':'
- Plugin class 'org.gradle.forceresolve.ForceDependencyResolutionPlugin': Cannot access project ':day3' from project ':'
changed the title [-]Support Project isolation using consumable configurations [/-][+]`ForceDependencyResolutionPlugin` incompatible with Project isolation[/+]on Feb 7, 2024
Any plans to address this now that Gradle 9.7 is graduating project isolation to incubating?
No concrete plans, no. Currently, this plugin requires -Dorg.gradle.isolated-projects=false for recent Gradle versions and -Dorg.gradle.unsafe.isolated-projects=false for older versions.
I will update the gradle/actions/dependency-submission action to set this value correctly for all Gradle versions.
Contributions to make the plugin compatible with isolated projects would be welcome.
Activity
[-]Support Project isolation using consumable configurations [/-][+]`ForceDependencyResolutionPlugin` incompatible with Project isolation[/+]bigdaz commentedon Feb 7, 2024
Thanks for the report. It's clear that the "resolve all dependencies" task could do with some rework.
As a workaround, are you able to set
-Dorg.gradle.unsafe.isolated-projects=falseto disable isolated projects?If so, I can add this as a parameter in the
dependency-submissionaction like this, pending a proper fix in this plugin.hfhbd commentedon Feb 11, 2024
Sure, setting this property works:
-Dorg.gradle.unsafe.isolated-projects=falseeygraber commentedon Jul 29, 2026
Any plans to address this now that Gradle 9.7 is graduating project isolation to incubating?
bigdaz commentedon Jul 31, 2026
No concrete plans, no. Currently, this plugin requires
-Dorg.gradle.isolated-projects=falsefor recent Gradle versions and-Dorg.gradle.unsafe.isolated-projects=falsefor older versions.I will update the
gradle/actions/dependency-submissionaction to set this value correctly for all Gradle versions.Contributions to make the plugin compatible with isolated projects would be welcome.