dhruv9b commented on issue #937: URL: https://github.com/apache/maven-enforcer/issues/937#issuecomment-5561818321
Hi @archiecobbs, I looked into this issue and agree that the current `RequireUpperBoundDeps` error message can be difficult to interpret, particularly when dependency management changes the resolved version. I reproduced the behavior and prepared a fix that changes the output from: `1.0.0 (managed) <-- 2.0.0` to: `1.0.0 (managed; requested 2.0.0)` This makes it clearer that `1.0.0` is the version selected by dependency management, while `2.0.0` is the version requested by that dependency path. I also added a regression test for the managed-version case and a short documentation clarification explaining the notation. I've opened a PR with the changes: https://github.com/apache/maven-enforcer/pull/1022 -- 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]
