[jira] [Closed] (MRESOLVER-363) Maven metadata is not updated in some cases

["Tamas Cservenak (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak closed MRESOLVER-363.
-------------------------------------
    Resolution: Not A Problem

This is actually not a bug, maven-resolver and maven behave correctly.

What may be questionable are the Maven defaults, as explained here: [https://maven.apache.org/ref/3.9.2/maven-settings/settings.html#releases] that are by default "never".

https://github.com/mojohaus/versions/pull/965The proper fix is done in plugin 

> 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
>             Fix For: 1.9.11
>
>
> 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)