[
https://issues.apache.org/jira/browse/MRESOLVER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832444#comment-17832444
]
ASF GitHub Bot commented on MRESOLVER-518:
------------------------------------------
cstamas opened a new pull request, #450:
URL: https://github.com/apache/maven-resolver/pull/450
I multiple V for same GA exist in graph, fail the operation.
---
https://issues.apache.org/jira/browse/MRESOLVER-518
> Add possibility to fail collection in case of version conflict
> --------------------------------------------------------------
>
> 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,
> 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)
