Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
1.9.10
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- links to