[
https://issues.apache.org/jira/browse/MRESOLVER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-518:
--------------------------------------
Description:
Currently Resolver "silently" resolves conflict based on "nearest" strategy,
without any assumption about selected version (simply the fact it is "nearer to
root" makes it win).
Extend this logic by ability to fail collection in case of version conflict,
version divergence and "version incompatibility" for start. As it may come
handy, and user may want to fix the build differently than Maven would.
was:
Currently Resolver "silently" resolves conflict based on "nearest" strategy,
without any assumption about selected version (simply the fact it is "nearer to
root" makes it win).
Extend this logic by ability to fail collection in case of version conflict,
for start. As it may come handy, and user may want to fix the build differently
than Maven would.
> Improvements for version selector
> ---------------------------------
>
> Key: MRESOLVER-518
> URL: https://issues.apache.org/jira/browse/MRESOLVER-518
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-11
>
>
> Currently Resolver "silently" resolves conflict based on "nearest" strategy,
> without any assumption about selected version (simply the fact it is "nearer
> to root" makes it win).
> Extend this logic by ability to fail collection in case of version conflict,
> version divergence and "version incompatibility" for start. As it may come
> handy, and user may want to fix the build differently than Maven would.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
