Ok, I see the root cause. Both xalan 2.7.1 and 2.7.2 were directly uploaded to Central, and those versions never existed on repository.apache.org. Then, in https://issues.apache.org/jira/browse/INFRA-24533?focusedCommentId=17717955&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17717955 the team finally created a profile so xalan could be published to repository.apache.org.
That caused metadata with a single 2.7.3 version which got replicated to Central. So I would ask Infra and Sonatype folks to collaborate on the best way fixing this. We could grab files from Central and publish them to repository.apache.org. That sounds like the most promising idea, however, I don't now if it will disrupt the synchronization from repository.apache.org to Central. Vladimir
