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

Tamas Cservenak commented on MRESOLVER-363:
-------------------------------------------

Re party: -I hand out- every guest can have a drink every 30 minutes. Whoever 
gets a drink, gets a sticker to his forehead with TS when he got it...
 * not present, I call you "get your a** here ASAP!"
 * present, w/ sticker on your forehead, I turn you toward my wifey, she checks 
the sticker, nods or nays ("give him a beer" or "no beer for him")
 * present, w/o sticker on your forehead (it fell off as you dance a lot), I 
grab an empty sticker, jot down Jan 1 1970 on it, stick it to your forehead and 
turn you toward my...

 

> 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