[ 
https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726690#comment-17726690
 ] 

Garret Wilson commented on MRESOLVER-363:
-----------------------------------------

{quote}If present, it means we have it (and checksums are hopefully according 
to checksum policy validated), so we can continue the work.{quote}

… unless we are keeping some separate "last-updated" flag, and something about 
the "last-updated" flag is fishy (or missing), which says, "uh, oh, we better 
check on this"!

{quote}IF you are present, i will ask my wife "Did Garret got his drink in last 
30 minutes?"{quote}

I think this is a good analogy, actually.

*If your wife doesn't know if Garret has had a drink in the last 30 minutes*, 
do you assume that I've had my drink in the last 30 minutes (and you assume 
that for the rest of the party, even if the party goes on all night), or do you 
think "it's probably better to assume that Garret has not had a drink in the 
last 30 minutes, and ask your wife to keep an eye out in the future"? I would 
argue the latter is a better approach, and that was core of my question.

Anyway, I've just had breakfast, but that drink you mentioned is already 
starting to sound good. 😅 haha I'll drop you a separate email about that. Have 
a good weekend!

> 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)

Reply via email to