Any idea why I'm getting this error when trying to...
# community-support
m
Any idea why I'm getting this error when trying to resolve the rocker plugin?
Copy code
Could 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...
e
doesn't the plugin portal redirect to jcenter for anything it doesn't have itself? e.g.
Copy code
curl -i <https://plugins.gradle.org/m2/com/example/nonexistent-gradle-plugin/0.0.1/nonexistent-gradle-plugin-0.0.1.pom>
redirects there too
in this case it seems that the
.pom
exists in the plugin portal but not the `.module`… which should be optional anyway
m
I understood it was redirecting to central now, yet, it seems strange that a plugin published in october 2023 would be broken wrt resolution on the portal
the issue clearly seems to be that the pom file states that the module file should be used, but it's not present 😕
it's not optional when the pom file says it's here
e
I didn't look at the pom itself but you're right, it does have the magic marker…
m
anyway, wanted to try rocker but if the plugin is broken then goodbye rocker
v
Sure it is optional, even with the marker unless something changed. And it would work properly if JCenter properly returned 404.
It returning 403 is probably yet again one of its typical outages.
And no, plugin portal is still not redirecting to MC, but still JCenter which is proxying MC.
e
I suppose in theory
Copy code
pluginManagement {
  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 not
v
That's could easily lead to problems with plugins actually using variants though.
e
yeah that's why I wouldn't want to do it globally for `gradlePluginPortal()`… I don't see a way around that though
v
Maybe if you declare a second repository with the same URL with the GMM disabled and that artifact as exclusive content
💡 1
But best to report and fix that plugins publication of course :-)
But yeah JCenter is answering all not found things with 403 instead of 404 right now.