Jakarta Staging Nexus shows deviating modification dates
Summary
During code analysis we encountered a bug in the Jakarta Staging Nexus, where modification dates of files are deviating partly for a new release of Jakarta EE 10 (10.0.0-RC1), which might be the reason this new artifact is not being fetched and the report is not generated in the jQAssistant tool.
Steps to reproduce
When opening the page https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/platform/jakarta.jakartaee-api/ the Last Modified column contains wrong timestamps for some of the meta data files!
Example: Site (https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/platform/jakarta.jakartaee-api/) shows lines: ... Name | Last Modified | Size | Description ... maven-metadata.xml Mon Nov 02 17:03:41 UTC 2020 297 ...
File maven-matedata.xml (https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/platform/jakarta.jakartaee-api/maven-metadata.xml) contains element: ... 20220209030723 ...
What is the current bug behavior?
The meta data file timestamps on the site deviate from the timestamp the 10.0.0-RC1 Artifact is gernerated and what is included within the file. Unclear at the moment are details about the use of the API by the jQAssistant tool, but deviations there might be the reason for it not fetching the root artifact at all.
What is the expected correct behavior?
Having consistent timestamps reflecting the correct last modified timestamp (from 10.0.0-RC1 in this case) in the files, the site and the API.
Relevant logs and/or screenshots
Mailing list root entry: https://www.eclipse.org/lists/jakartaee-platform-dev/msg03246.html
jQAssistant repo: https://github.com/jqassistant-demo/jakarta-ee-dependencies
jQAssistant issue: https://github.com/jqassistant-demo/jakarta-ee-dependencies/issues/1
Would this be fixed with a migration from Nexus 2 to Nexus 3 automatically?