You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "cstamas (via GitHub)" <gi...@apache.org> on 2023/02/28 14:58:14 UTC

[GitHub] [maven-resolver] cstamas commented on a diff in pull request #261: [MRESOLVER-333] Better errors about artifact availability

cstamas commented on code in PR #261:
URL: https://github.com/apache/maven-resolver/pull/261#discussion_r1120201987


##########
maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultArtifactResolver.java:
##########
@@ -384,9 +384,8 @@ private List<ArtifactResult> resolve(
 
             if (local.getFile() != null) {
                 LOGGER.info(
-                        "Artifact {} is locally present, but unavailable, verifying availability of {} from {}",
+                        "Artifact {} is present in local repository, but cached from a repository ID that is unavailable in current build context, verifying that is downloadable from {}",

Review Comment:
   The ID is what matters sadly. If a user has same URL once defined as "repo" and once as "remote-repo", despite same URL, same will happen. On the other hand, there is no ID, there may be IDs (plural), so enumerate them all like "is unavailable as it was downloaded/verified from repo A, B, C, but your project build context has D, E, F"... would be way too much.



-- 
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