reda-alaoui opened a new pull request, #1085:
URL: https://github.com/apache/maven-enforcer/pull/1085
Closes #1084
Before this change, `requireUpperBoundDeps` let a version set in
`dependencyManagement` drift above every version the dependency tree requests,
for example after Renovate or Dependabot bumped it.
This change adds `failWhenManagedVersionIsAboveRequested` (default `false`).
When set, the rule fails if a version managed by the project or one of its
parents is above every version requested for that dependency. It does not check:
- versions managed by an imported BOM. They are told apart by the model id
Maven records as the source of each managed version (`getLocation("version")`),
compared with the raw ids of the project and its parents;
- dependencies the project declares directly;
- dependencies listed in `excludes`, left out by `includes`, or reached only
through `excludedScopes`.
A requested version range containing the managed version counts as
satisfied. The error lists the paths to the dependency and suggests the highest
requested version.
Covered by unit tests and two ITs:
`require-upper-bound-deps_managed-above-requested_failure` and
`require-upper-bound-deps_managed-above-requested-by-bom_success`.
---
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](https://www.apache.org/licenses/LICENSE-2.0)
check one of the following:
- [ ] I hereby declare this contribution to be licensed under the [Apache
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
- [ ] I hereby declare that I have filed an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]