[
https://issues.apache.org/jira/browse/MRESOLVER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694682#comment-17694682
]
ASF GitHub Bot commented on MRESOLVER-333:
------------------------------------------
cstamas commented on code in PR #261:
URL: https://github.com/apache/maven-resolver/pull/261#discussion_r1120579958
##########
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:
No, as to check you need to know the repo id. Simply put: the check is
iteration over (current project defined) remote repositories, and ends as
"unavailable" if none matched. See enhanced lrm find (overrides simple lrm find
method) and below.
> Distinguish better resolver errors for artifact availability
> ------------------------------------------------------------
>
> Key: MRESOLVER-333
> URL: https://issues.apache.org/jira/browse/MRESOLVER-333
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.6
>
>
> Improve resolver emitted errors to detail more about the state (the error)
> how resolver came up with it. Example issues:
> * MNG-5185
> * MNG-7001
> The "artifact availability check" is widely misunderstood.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
