[
https://issues.apache.org/jira/browse/MRESOLVER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833477#comment-17833477
]
ASF GitHub Bot commented on MRESOLVER-518:
------------------------------------------
cstamas commented on code in PR #450:
URL: https://github.com/apache/maven-resolver/pull/450#discussion_r1549387693
##########
maven-resolver-api/src/main/java/org/eclipse/aether/collection/UnsolvableVersionConflictException.java:
##########
@@ -42,9 +42,25 @@ public class UnsolvableVersionConflictException extends
RepositoryException {
* Creates a new exception with the specified paths to conflicting nodes
in the dependency graph.
*
* @param paths The paths to the dependency nodes that participate in the
version conflict, may be {@code null}.
+ * @deprecated Use {@link #UnsolvableVersionConflictException(String,
Collection)} instead.
Review Comment:
No existing code uses this deprecated ctor (not counting deprecated class),
or new one with `null` param, it is left merely for binary compatibility. In
fact, this exception is so special, that nothing else uses it.
> 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
> Assignee: 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)
