[ https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726591#comment-17726591 ]
ASF GitHub Bot commented on MRESOLVER-363: ------------------------------------------ cstamas commented on PR #291: URL: https://github.com/apache/maven-resolver/pull/291#issuecomment-1564236459 This is completely wrong, and resolver DOES behaves correctly, as update policy is "never" > 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 > Assignee: Tamas Cservenak > Priority: Major > Fix For: 1.9.11 > > > Seems when update check for metadata happens, and: > * maven-metadata XML is present, but > * resolver-status.properties is not, OR was created by maven-compat, that > uses different key for lastUpdated. Effectively the value of lastUpdated is > not present. > 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)