Because of some bug under Windows I need to use the recently published version 1.1.1 of the plugin
gradle-eclipseconfig. While that plugin is shown on the web page already and one can have a directory listing, it doesn’t resolve in
build.gradle. I get the following errors:
Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find org.standardout:gradle-eclipseconfig:1.1.1. Searched in the following locations: - https://plugins.gradle.org/m2/org/standardout/gradle-eclipseconfig/1.1.1/gradle-eclipseconfig-1.1.1.pom - https://plugins.gradle.org/m2/org/standardout/gradle-eclipseconfig/1.1.1/gradle-eclipseconfig-1.1.1.jar Required by: project :de.am_soft.build.gradle > org.standardout.eclipseconfig:org.standardout.eclipseconfig.gradle.plugin:1.1.1
I tried to download the mentioned files manually and got the following XML from the web server:
<?xml version="1.0" encoding="UTF-8"?> <Error> <Code>NoSuchKey</Code> <Message>The specified key does not exist.</Message> <Key>org.standardout/gradle-eclipseconfig/1.1.1/dfbda94f124f7cd5b16e0151aa77e524193fc45f5c9b16387310d4745a60c0d1/gradle-eclipseconfig-1.1.1.pom</Key> <RequestId>80076A0B79DE5448</RequestId> <HostId>WVN/7sCsnDE48LpSVyEXIh8BzgQTQk4veKxxZfQBm4X1p1sDcZFAj4/Uec6RZ5xKMCZOiyIz2Rg=</HostId> </Error>
Has the plugin been published properly or is there some error? Does it still take some time to finish the publishing and I simply need to wait? Might it have something to do with new approval of plugins needed?
The other files of the plugin can easily be downloaded without the formerly quoted XML response. But those are from 2016 already. So if the publishing went wrong for some reason, I would like to notify the maintainer of that plugin to have another look.