Gradle 8.1.1: Resolution of the configuration ... was attempted from a context different than the project context

[matthiaskraaz]

I get lots and lots of message of this type for varying configurations when running the dependencyCheckAggregate task:

Resolution of the configuration :jsource:osis:runtime:server:spotbugsPlugins 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. See https://docs.gradle.org/8.1.1/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details

[jeremylong]

I've tried a few times to create a project that replicates this issue and I can't seem to get the warning. Does anyone have a project I can use to reproduce this issue?

[chadlwilson]

It's quite likely replicable on GoCD at https://github.com/gocd/gocd/tree/25.3.0 (not master as that has been moved to Gradle 9 where the failure mode is different and need to disable parallelization) but that might be a bit of a pain to get going.

If so, I can create a simpler one at some point, probably tomorrow.

You might need to enable org.gradle.parallel=true or --max-workers=4 to see it IIRC, since Gradle doesn't understand that the aggregate task is depending on configurations in other projects which might not be resolved before aggregate task configures itself in parallel to other tasks.

[chadlwilson]

@jeremylong Here's an example project: https://github.com/chadlwilson/gradle-parallel-config-issue

At root the issue likely involves going down an inter-project dependency rabbit-hole and figuring out how to add the inter-project dependencies from aggregateProject --> childProjectConfiguration(s) | childProjectFile(s) safely.

I'm not an expert yet, but generally I think it probably means

• selecting the set of projects and configurations at "configuration" time (via all the skip/scan logic)
  • so build on fix: resolve warnings about access Task.Project in gradle 8+ #474 basically
  • currently it's all merged into execution phase, so needs to be factored out
• when the plugin determines that a project and configuration needs to be scanned:
  • may need to create an extension consumable configuration for any matching configuration when working from root project -> other project
    • basically the "declaring custom extension configurations" path like https://dev.to/autonomousapps/configuration-roles-and-the-blogging-industrial-complex-21mn ...
    • https://docs.gradle.org/8.14.3/userguide/how_to_share_outputs_between_projects.html#variant-aware-sharing documents this approach, but with the even-more-complex variant aware style.
• an alternative is possibly to programmatically add a task to each project, which itself depends on the set of configurations; and then use an Output of that task as an input to dependencyCheckAggregate. It's possibly a bit messy, as outputs are intended to be files; and cacheable - not really what we want here.
  • if the aggregate task depended on a set of analyze tasks (perhaps running in a different mode than when run directly), and the analyze tasks declared their dependencies on relevant resolvable configurations in the same project that also might work; however it'd probably lead to more parallelism to control.