Fix BOM ref values in dependency graph warning log#5909
Open
Zureno wants to merge 2 commits intoDependencyTrack:masterfrom
Open
Fix BOM ref values in dependency graph warning log#5909Zureno wants to merge 2 commits intoDependencyTrack:masterfrom
Zureno wants to merge 2 commits intoDependencyTrack:masterfrom
Conversation
Signed-off-by: Zureno <pranshu21freak@gmail.com>
Signed-off-by: Zureno <pranshu21freak@gmail.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Contributor
Author
|
Happy to split the changes into separate PRs if preferred. |
nscuro
reviewed
Mar 15, 2026
nscuro
requested changes
Mar 15, 2026
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences |
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
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
Fixes the warning log emitted when a direct dependency BOM ref cannot be resolved during dependency graph processing.
The warning message in
resolveDirectDependenciesJson(...)currently formats the parent BOM ref and the direct dependency BOM ref in reverse order. This makes troubleshooting more difficult because the unresolved reference appears in the wrong position in the log output.This change corrects the formatting order so the unresolved direct dependency BOM ref is reported first, followed by the BOM ref whose dependencies are being processed.
Addressed Issue
N/A – Logging clarity improvement.
Additional Details
In
resolveDirectDependenciesJson(...), the warning currently uses:.formatted(dependencyBomRef, directDependencyBomRef)
Checklist