[
https://issues.apache.org/jira/browse/MRESOLVER-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694513#comment-17694513
]
Tamas Cservenak edited comment on MRESOLVER-333 at 2/28/23 12:37 PM:
---------------------------------------------------------------------
For start, distinguish between "absent" and "present, but unavailable" cases in
error message, this way users will approach us to explain "why is artifact
present but unavailable?". The answer is simple: rebuild with empty local
repository (and build will fail as well). Longer answer is: the repository IDs
from where the cached "present" artifact originates from, and remote repository
IDs of your current failing build has no intersection (the repository IDs still
can be off, like "atlassian" vs "atlassian-forge" etc!).
was (Author: cstamas):
For start, distinguish no present and present but unavailable cases in error
message, this way users will approach us to explain "why is artifact present
but unavailable?". The answer is simple: rebuild with empty local repository
(and build will fail as well). Longer answer is: the repository IDs from where
the cached "present" artifact originates from, and remote repository IDs of
your current failing build has no intersection (the repository IDs still can be
off, like "atlassian" vs "atlassian-forge" etc!).
> 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)
