[
https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726685#comment-17726685
]
Tamas Cservenak edited comment on MRESOLVER-363 at 5/26/23 5:07 PM:
--------------------------------------------------------------------
Well, TS_NEVER is January 1, 1970 and TS_UNKNOWN is January 1, 1970 + 1
millisecond (0 and 1 long values respectively) :)
But none of those will update, if policy is "never", would not update even if
TS would be 0BC, as long as policy in effect is "never".
===
EDIT: oh, sorry, I think I get it: so you ask why differentiate "not present"
and "present, but no idea when arrived"? Well, If not present, we need to do
something about it (grab it). If present, it means we have it (and checksums
are hopefully according to checksum policy validated), so we can continue the
work after we applied the "update policy".
And we are back in philosophical topic: i have a party, am dealing out drinks
every 30 minutes. You are invitee.
IF you did not appear yet, I grab a phone, and call you.
IF you are present, i will ask my wife "Did Garret got his drink in last 30
minutes?"
was (Author: cstamas):
Well, TS_NEVER is January 1, 1970 and TS_UNKNOWN is January 1, 1970 + 1
millisecond (0 and 1 long values respectively) :)
But none of those will update, if policy is "never", would not update even if
TS would be 0BC, as long as policy in effect is "never".
===
EDIT: oh, sorry, I think I get it: so you ask why differentiate "not present"
and "present, but no idea when arrived"? Well, If not present, we need to do
something about it (grab it). If present, it means we have it (and checksums
are hopefully according to checksum policy validated), so we can continue the
work.
And we are back in philosophical topic: i have a party, am dealing out drinks
every 30 minutes. You are invitee.
IF you did not appear yet, I grab a phone, and call you.
IF you are present, i will ask my wife "Did Garret got his drink in last 30
minutes?"
> 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)
