Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168534190
General rule of thumb is that a change in resolution will definitely not go
in if it changes the default behaviour within a minor version. First smoke test
is making sure the ITs pass, second smoke test is that I run it against 40-50
projects I use as a sampling. So at least make sure the core integration tests
pass. If it does change resolution within a minor version then it needs to be
activated consciously on the users part. If this is deemed an improvement it
can become something activated by default in 4.x possibly.
For better or worse the way Maven resolves dependencies currently is how it
works for everyone. Making changes to this and possibly selecting different
versions of dependencies based on different rules can potentially break a lot
of people.
---
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
