melix
04/17/2024, 6:12 AMCould not resolve all files for configuration ':classpath'.
> Could not resolve com.fizzed:rocker-gradle-plugin:1.4.0.
Required by:
project : > com.fizzed.rocker:com.fizzed.rocker.gradle.plugin:1.4.0
> Could not resolve com.fizzed:rocker-gradle-plugin:1.4.0.
> Could not get resource '<https://plugins.gradle.org/m2/com/fizzed/rocker-gradle-plugin/1.4.0/rocker-gradle-plugin-1.4.0.module>'.
> Could not GET '<https://jcenter.bintray.com/com/fizzed/rocker-gradle-plugin/1.4.0/rocker-gradle-plugin-1.4.0.module>'. Received status code 403 from server: Forbidden
This is https://plugins.gradle.org/plugin/com.fizzed.rocker.
In particular I'm surprised it redirects to bintray, for a plugin released in october 2023, where bintray was long dead...ephemient
04/17/2024, 6:23 AMcurl -i <https://plugins.gradle.org/m2/com/example/nonexistent-gradle-plugin/0.0.1/nonexistent-gradle-plugin-0.0.1.pom>
redirects there tooephemient
04/17/2024, 6:25 AM.pom
exists in the plugin portal but not the `.module`… which should be optional anywaymelix
04/17/2024, 6:26 AMmelix
04/17/2024, 6:27 AMmelix
04/17/2024, 6:27 AMephemient
04/17/2024, 6:28 AMmelix
04/17/2024, 6:31 AMVampire
04/17/2024, 6:54 AMVampire
04/17/2024, 6:55 AMVampire
04/17/2024, 6:55 AMephemient
04/17/2024, 6:56 AMpluginManagement {
repositories {
gradlePluginPortal {
metadataSources {
ignoreGradleMetadataRedirection()
could help too but I'm not sure if there's a way to do that for just one artifact or notVampire
04/17/2024, 6:56 AMephemient
04/17/2024, 6:57 AMVampire
04/17/2024, 6:57 AMVampire
04/17/2024, 6:58 AMVampire
04/17/2024, 7:04 AM