[
https://issues.apache.org/jira/browse/MRESOLVER-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726579#comment-17726579
]
ASF GitHub Bot commented on MRESOLVER-363:
------------------------------------------
cstamas opened a new pull request, #291:
URL: https://github.com/apache/maven-resolver/pull/291
In case of metadata, when XML file exists, but the
resolver-status.properties file does not, or the "lastUpdated" key is not
found, the XML is never updated.
NOTE: UT fails, we need more discussion about this, see JIRA issue.
---
https://issues.apache.org/jira/browse/MRESOLVER-363
> 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)
