[ https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726683#comment-17726683 ]
Garret Wilson edited comment on MRESOLVER-363 at 5/26/23 4:55 PM: ------------------------------------------------------------------ {quote}2. that's exactly what happens (with a twist: file is not present -> go grab it; file is present but no lastUpdated -> let policy decide){quote} But you didn't answer my question. That's _not_ what happens today, because it has the "twist" you mentioned. You say you have this: {quote}file is present but no lastUpdated -> let policy decide{quote} I am asking you very specifically: **What harm would come if we change it to the following?** _file is present but no lastUpdated -> default to a lastUpdated of January 1, 1970_ {quote}Also observe this UT, that would fail if in case TS_NEVER would be returned instead of TS_UNKNOWN{quote} But I'm not proposing you return {{TS_NEVER}} instead of {{TS_UNKNOWN}}. I'm asking what bad would happen if you return "January 1, 1970" instead of {{TS_UNKNOWN}}? was (Author: garretwilson): {quote}2. that's exactly what happens (with a twist: file is not present -> go grab it; file is present but no lastUpdated -> let policy decide)\{quote} But you didn't answer my question. That's _not_ what happens today, because it has the "twist" you mentioned. You say you have this: {quote}file is present but no lastUpdated -> let policy decide{quote} I am asking you very specifically: **What harm would come if we change it to the following?** _file is present but no lastUpdated -> default to a lastUpdated of January 1, 1970_ {quote}Also observe this UT, that would fail if in case TS_NEVER would be returned instead of TS_UNKNOWN{quote} But I'm not proposing you return {{TS_NEVER}} instead of {{TS_UNKNOWN}}. I'm asking what bad would happen if you return "January 1, 1970" instead of {{TS_UNKNOWN}}? > 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)