We have a repository in nexus sonatype repository, the type is proxy and format is maven2, this repository is used to mirror from upstream repo Central Repository: .After migration last month, our users said that the sha1 value of maven-metadata.xml is different with maven-metadata.xml.sha1. is there any method to fix it?
One thought I have is that your repository may have a changed the Maximum Metadata Age property which has either disabled checking for upstream changes or has a long delay.
Aside from that you could try deleting the checksum and metadata files and allow Nexus to re-proxy them to see if it resolves the issue.
To give more info about this case, the “Maximum Metadata Age” is set to 120 minutes.
This setting I expect is applied both to maven-metadata.xml files, and their checksum files…?
One weird thing about this is that some of the metadata files belong to G:As that haven’t been updated in years. E.g. we see wrong metadata checksums in following G:As that were last modified in 2017 / 2015:
Both sha1 and md5 checksum are wrong, and they have not corrected in a span of a week since we noticed they are wrong. I fail to understand how they could possibly be not invalidated & re-downloaded during that time given the “Maximum Metadata Age” is 120 minutes.
The “Maximum component age” is -1, which I assume is not relevant to the metadata files and their checksums.
Anyway, thanks for the suggestions!