Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168543843
Perhaps a POM property with predefined name could activate this behaviour
in 3.x? In this way it can be set on a per-project basis as well as global
(with properties injected via settings.xml).
In case when a change of DependencyManagement model is allowed (4.x?) -
this might be better approach in the long run as this info can be reused in the
maven dependency plugin (to show where managed version comes from) and perhaps
will allow to introduce pluggable dependency resolution strategy
(nearest-match, newest-version, etc.) in both dependency and
dependencyManagement sections.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
