[
https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726687#comment-17726687
]
Garret Wilson edited comment on MRESOLVER-363 at 5/26/23 5:07 PM:
------------------------------------------------------------------
{quote}Well, TS_NEVER is January 1, 1970 and TS_UNKNOWN is January 1, 1970 + 1
millisecond (0 and 1 long values respectively){quote}
(sigh) That missed the point of my question (and illustrates the peril of
carving out certain valid values and giving them special semantics for return
codes).
Pretend my question said I'm asking what bad would happen if you return "*two
milliseconds past* January 1, 1970" instead of {{TS_UNKNOWN}}, or the date
Maven was first released, or any other arbitrary date in the past.
But never mind. I know we both have other work to do. I'll look for the
Versions Maven Plugin update.
was (Author: garretwilson):
{quote}Well, TS_NEVER is January 1, 1970 and TS_UNKNOWN is January 1, 1970 + 1
millisecond (0 and 1 long values respectively){quote}
(sigh) That missed the point of my question (and illustrates the peril of
carving out certain valid values and giving them special semantics for return
codes).
Pretend my question said I'm asking what bad would happen if you return "*two
milliseconds past* January 1, 1970" instead of {{TS_UNKNOWN}}, or the date
Maven was created, or any other arbitrary date in the past.
But never mind. I know we both have other work to do. I'll look for the
Versions Maven Plugin update.
> 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)
