[ https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726684#comment-17726684 ]
Garret Wilson commented on MRESOLVER-363: ----------------------------------------- Look maybe I'm still not explaining my question well. I don't want to keep insisting and make people irritated. I'll just live with {{-U}} for the moment, and then you say that Versions Maven Plugin will have some changes that will make {{-U}} not necessary. Great. Thanks for working on this. > 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 > > 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)