Closed JLLeitschuh closed 1 year ago
@bigdaz any idea why I was experiencing this? What was I missing?
No, I don't know why you were missing many resolved configurations from your generated JSON. But if you look at the JSON that was generated from an earlier self-check run, you can see many, many configurations being resolved: https://github.com/gradle/github-dependency-extractor/actions/runs/4601760360. (The generated JSON is saved as a build artifact).
Later runs should express the same dependency information, but will be collapsed into a per-project manifest.
Does re-runing the same build multiple times cause certain configurations to not get re-resolved?
Does re-runing the same build multiple times cause certain configurations to not get re-resolved?
Without configuration-cache enabled, this doesn't seem likely, assuming the same tasks are targeted and the build succeeds (some task input may not be resolved for a failed build).
I can't explain why testRuntimeClasspath
was reported as resolved in the build scan but is missing from your JSON.
Running the self-test the JSON doesn't match up with the build scan
https://ge.gradle.org/s/byrea6vrsycvy/dependencies?toggled=W1swXV0