[
https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726404#comment-17726404
]
Tamas Cservenak edited comment on MRESOLVER-363 at 5/25/23 9:50 PM:
--------------------------------------------------------------------
It was present, but created with maven-compat, that uses different key for
lastUpdated, so effectively, code behaved like not present, as key for
lastUpdated nor value for it was not found.
was (Author: cstamas):
It was present, but created with maven-compat, that uses different key for
lastUpdated, so effectively, code behaved like not present, as key nor
lastUpdated value was not found.
> Maven metadata is not updated in some cases
> -------------------------------------------
>
> Key: MRESOLVER-363
> URL: https://issues.apache.org/jira/browse/MRESOLVER-363
> Project: Maven Resolver
> Issue Type: Bug
> Affects Versions: 1.9.10
> Reporter: Tamas Cservenak
> Priority: Major
>
> Seems when update check for metadata happens, and:
> * maven-metadata XML is present, but
> * resolver-status.properties is not
> The update check falsely DO NOT check for update, as it will end up with
> update policy "never" in update policy analyzer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
