[
https://issues.apache.org/jira/browse/MRESOLVER-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783298#comment-17783298
]
Tamas Cservenak commented on MRESOLVER-428:
-------------------------------------------
I would leave out the "not yet synced to central" story from this, as it has
many other issues as well (sadly, CENTRAL JIRA is not public, but I reported
this several times): in Central _first_ the metadata is synced, and only then
the content. This means that use cases like "versions display updates" would
discover the not-yet-synced artifact version (as metadata is synced) while
artifact content is not present.
This is why maven itself is very strict with the order of deployment (metadata
must be latest), but Central clearly violates this...
> Handle differently the "memoized HTTP 404" cached responses
> -----------------------------------------------------------
>
> Key: MRESOLVER-428
> URL: https://issues.apache.org/jira/browse/MRESOLVER-428
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> Currently, mvn local repo will "remember" that a repo reported 404 for
> artifact not present, and this fact is cached using ordinary update policy.
> To make mvn retry, -U is needed, that again, is too heavy handed, as it will
> force update always policy for everything...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
