gradle/github-dependency-graph-gradle-plugin

`ForceDependencyResolutionPlugin` incompatible with Project isolation

Opened this issue · 2 comments

hfhbd commented

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 ':'

Sample code: https://github.com/hfhbd/advendOfCode
failing build: https://github.com/hfhbd/advendOfCode/actions/runs/7795902785/job/21259617710

bigdaz commented

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=false to disable isolated projects?

If so, I can add this as a parameter in the dependency-submission action like this, pending a proper fix in this plugin.

hfhbd commented

Sure, setting this property works: -Dorg.gradle.unsafe.isolated-projects=false

  • 👍1