feat(manager/gradle): Use dependencies task when generating verification metadata #29602
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
As discussed here, use
dependencies
task when generating verification metadata.Context
Currently, the
help
task is called to generate theverification-metadata.xml
(e.g../gradlew --write-verification-metadata sha256 help
). Gradle is lazy and may not evaluate the required dependencies:In my tests, using the built-in
dependencies
task instead ofhelp
works quite well (./gradlew --write-verification-metadata sha256 dependencies
). Thedependencies
task is also called for lockfile generation.Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: