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

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

{quote}How is this difficult to resolve? If we update Maven's behavior so that 
if resolver-status.properties is missing (or does not have the correct 
"last-updated" flag), then instead of doing nothing, Maven proceeds as if the 
"last-updated" value is January 1, 1970. Everything works as before if 
"last-updated" is present. If not, then the Versions Maven Plugin related bug 
is fixed and going forward there will be a "last-updated" flag. It's probably a 
single line of code (not counting brackets). What is the downside?{quote}

In fact, if you agree to at least _consider_ this approach, assign it to me and 
I'll be happy to look into it and file a pull request if it works out. Checking 
for files and defaulting values and such is something I do day-in and day-out, 
so it's right up my alley. I can't imagine this could be too difficult. Just 
find out where it's looking for the {{resolver-status.properties}} file, and 
add an {{else}} to the "property not found" part. But only if you would 
consider it; I don't want to do it if it's out of the question to be accepted.

> 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