Github user ifedorenko commented on the pull request:
https://github.com/apache/maven/pull/57#issuecomment-120415902
What will happen when projects using new/custom version range resolution
strategy are deployed to shared repository like Central? Won't this break
consumers of project artifacts?
For example, say my project uses odd/even versioning convention to
distinguish between developer and stable versions and I implemented custom
range resolver to enforce this convention. Since consumers of my project's
artifacts will have no knowledge of the versioning scheme I use, they may
resolve wrong transitive dependencies.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
