fix: gradle ca produces two versions of the same package #131
Conversation
This file contains 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
Signed-off-by: Zvi Grinberg <zgrinber@redhat.com>
zvigrinberg
force-pushed
the
hotfix/fix-gradle-ca-no-ver
branch
from
79bc4ef to
40edc74
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
When invoking Compoent analysis for gradle , with build.gradle containing same artifact twice each time with different version, then sbom is generated with these 2 versions ,which is wrong.
the fix resolves this conflict by using data comes from gradle dependencies command, and then dropping the version that wasn't the resolution for the conflict.
Checklist