Override conflicting dependencies with the finally used ones. #7028
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
sdedic
added
Maven
MartinBalin
approved these changes
Feb 5, 2024
dbalek
approved these changes
Feb 13, 2024
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.
There's a bug in Maven dependency reporter. In case of conflicting artifacts, the next children were taken from the real dependency, but the node itself was still added to the tree.
So in case that 4rd party dependency
gson:gson:jar:2.8.6conflict with project-mandated2.10.1, 2.8.6 is actually used by project. Maven reporter implementation traverses below using children from 2.10.1, butgson:jar:2.8.6was still included in the tree.This may cause false vulnerability reports in ADM.