You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "gnodet (via GitHub)" <gi...@apache.org> on 2024/04/03 09:48:55 UTC

Re: [PR] [MRESOLVER-518] Version selector improvements [maven-resolver]

gnodet commented on code in PR #450:
URL: https://github.com/apache/maven-resolver/pull/450#discussion_r1549377629


##########
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:
   I don't see the point of deprecating this constructor, since it forces the addition of a `null` parameter and lead the user to a change which is useless, given the message has a default value.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org