[ https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726402#comment-17726402 ]
Garret Wilson commented on MRESOLVER-363: ----------------------------------------- The description indicates that {{resolver-status.properties}} is not present. I understand that this is part of the scenario used initially to reproduce this problem in [Versions Maven Plugin Issue #959|https://github.com/mojohaus/versions/issues/959], but I just wanted to mention that for the original case {{resolver-status.properties}} was in fact present and this problem still presented itself. > 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)