[
https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726674#comment-17726674
]
Garret Wilson edited comment on MRESOLVER-363 at 5/26/23 4:22 PM:
------------------------------------------------------------------
I understood and agree with most everything you said in the previous comment,
but I'm still not understanding how it is relevant. Perhaps my trying to
understand Maven's concept of "change policy" without researching into the code
may be futile, and may even be beside the point.
So let me sidestep all the philosophy and break it down to two simple
questions, based upon {_}current Maven functionality{_}:
1. Is there ever a situation in which it is valid for Maven to consider
{{{}resolver-status.properties{}}}? (I'm not asking you what that situation is,
because it gets into a long discussion about things that I'm still not
understanding.) I'm trying to simplify this: {*}is there ever a situation, yes
or no{*}, in which it is valid for Maven to look for and use a "last-updated"
flag in {{{}resolver-status.properties{}}}? (I added bold only to be clear
about what question I am asking.)
2. _If_ the answer to #1 is "yes, in some circumstances it would be valid for
Maven to consider a last-updated flag in {{{}resolver-status.properties{}}}",
my second question is: what would be the downside if, in those circumstances
(whatever they are), if Maven cannot find a "last-updated" flag in
{{{}resolver-status.properties{}}}, to default to some "last-updated" date in
the past such as January 1, 1970? *What harm would come from this?*
was (Author: garretwilson):
I understood and agree with most everything you said in the previous comment,
but I'm still not understanding how it is relevant. Perhaps my trying to
understand Maven's concept of "change policy" without researching into the code
may be futile, and may even be beside the point.
So let me sidestep all the philosophy and break it down to two simple
questions, based upon {_}current Maven functionality{_}:
1. Is there ever a situation in which it is valid for Maven to consider
{{{}resolver-status.properties{}}}? (I'm not asking you what that situation is,
because it gets into a long discussion about things that I'm still not
understanding.) I'm trying to simplify this: {*}is there ever a situation, yes
or no{*}, in which it is valid for Maven to look for and use a "last-updated"
flag in {{{}resolver-status.properties{}}}? (I added bold only to be clear
about what question I am asking.)
2. _If_ the answer to #1 is "yes, in some circumstances it would be valid for
Maven to consider a last-updated flag in {{{}resolver-status.properties{}}}",
my second question is: what would be the downside if, in those circumstances
(whatever they are), if Maven cannot find a "last-updated" flag in
{{{}resolver-status.properties{}}}, to default to some "last-updated" date in
the past such as January 1, 1900? *What harm would come from 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)
