[
https://issues.apache.org/jira/browse/MRELEASE-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002896#comment-15002896
]
Osvaldo Pinali Doederlein commented on MRELEASE-929:
----------------------------------------------------
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.
> 2.5.3 release is broken in maven-central
> ----------------------------------------
>
> Key: MRELEASE-929
> URL: https://issues.apache.org/jira/browse/MRELEASE-929
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 2.5.3
> Reporter: Osvaldo Pinali Doederlein
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
