[MRELEASE-929] 2.5.3 release is broken in maven-central

[jira-importer]

Osvaldo Pinali Doederlein opened MRELEASE-929 and commented

I now get this trying to build a pom that depends on 2.5.3:

[WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.5.3 is missing, no dependency information available

Checking the repo,
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/

It's missing some of the sign files, e.g. .asc.md5.

---

Affects: 2.5.3

0 votes, 5 watchers

[jira-importer]

Manfred Moser commented

This must be a connection issue on your side. The pom files and all other files are there.

[jira-importer]

Osvaldo Pinali Doederlein commented

Reopening because this is more complex than I had initially realized. The problem involves google's new maven-central mirror, but I think the main repo is at fault too. First the 2.5.3 release is definitely missing some files:

1. curl https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/
2. curl https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.2/

2.5.3 lists only 16 files, instead of 25 like 2.5.2, 2.5.1, etc.

And when I check the Google mirror, it's missing 2.5.3 complexely, but this is not normal because 2.5.3 has been around for some time already. My guess is that our mirror synchronized is validating the files and skipping releases that look invalid, which seems the be the case here. I'm filing a bug internally to investigate.

[jira-importer]

Karl Heinz Marbaise commented

Unfortunately Osvaldo is right...the number of files is different..and it is not a connection issue i can see the same things here (from germany)... If you take a look into the original apache repository https://repository.apache.org/content/repositories/releases/org/apache/maven/plugins/maven-release-plugin/2.5.3/ you will see the same number of artifacts as in central...If you take a look at https://repository.apache.org/content/repositories/releases/org/apache/maven/plugins/maven-release-plugin/2.5.2/ there is larger number of files in there...

In the end it looks like that during the release some files have not been generated or not being uploaded to apache release repository...so only this content from apache repository has been synched to central...

It looks like the complete release of 2.5.3 is missing several files ...

I have created a support ticket for Maven Central https://issues.sonatype.org/browse/OSSRH-18858, also informed INFRA https://issues.apache.org/jira/browse/INFRA-10759...

Thanks for reporting this Osvaldo...

The missing artifacts in the google mirror i'm not sure about at the moment...

[jira-importer]

Anders Hammar commented

Looks as this is fixed now.

[jira-importer]

Karl Heinz Marbaise commented

if you check the infra ticket it is not fully fixed...

[jira-importer]

Hervé Boutemy commented

1. from my location, there does not seem to be any issue in https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.5.3/ currently. I don't know if it's a question of location (central uses geo ip) or transient issue that is solved

2. I suppose INFRA won't be able to do anything with this issue, since if there is an issue, it's more at central level: https://issues.sonatype.org/projects/MVNCENTRAL

[jira-importer]

Karl Heinz Marbaise commented

In the meantime the first part of the INFRA ticket has been solved (which you can see by the changed date of the artifact .md5, .sha1
And yes INFRA can trigger to recreate the missing .md5, .sha1 files via Nexus GUI and afterwards they will be synched to central....As in INFRA ticket described there are other artifacts which lack .md5 and .sha1 files...Furthermore i have added the ticket for Maven central (https://issues.sonatype.org/browse/OSSRH-18858) where i started with the journey...

[jira-importer]

Hervé Boutemy commented

thanks for the explanations: I completely missed the details :)

[jira-importer]

Karl Heinz Marbaise commented

So INFRA ticket is completed. So we have to wait for sync to central.

[jira-importer]

Karl Heinz Marbaise commented

All artifact checksums (md5, sha1) have been regenerated by INFRA (Thanks for their help)... and they have synched to central.