fix: problem with gradle version resolution#141
Merged
Conversation
ruromero
requested changes
Jun 16, 2025
ruromero
left a comment
ruromero
left a comment
Collaborator
There was a problem hiding this comment.
Do you mind reviewing my comments? Thanks
ruromero
requested changes
Jun 16, 2025
Signed-off-by: Chao Wang <chaowan@redhat.com>
soul2zimate
force-pushed
the
gradle_resolution_main
branch
from
1a41c6c to
4e13f06
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Refactor how the Gradle dependencies are resolved because as the full tree is available in both component and stack analysis we can use the right trees instead of just the api / implementation listings. This helps resolving the correct versions.
With that it is also possible to include the correct scope (required / optional) to the sbom
Related issue (if any):
Checklist
Additional information
cc @olavtar @zvigrinberg in case you have some free time to review 😄 Thanks.