#291 display-dependency-updates: introduce switch processDependencyManagementTransitive #588
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
…ay-dependency-updates
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.
adding a new switch
processDependencyManagementTransitivetodisplay-dependency-updatesgoal, with same semantics as it was added with #129 todependency-update-reportthe default value is true which reflects the current behavior (backward compatibility).
if set to false, the dependency check is done using the "original model", meaning dependencies with "import" scope (often called "BOM") are not interpolated and checked itself, instead of the transitive dependencies they import (over which the user has no direct control).
please note: this works as described if the BOM import dependency is declared in the current POM. if such a dependency is declared in the parent POM, it works a bit different: if the current POM references dependencies declared in the POM references in the parent POM, the versions updates of those dependencies are reported, not of the BOM itself. still, with this new feature working with huge lists of transitive dependencies from BOMs gets much easier.
Fixes #291