tbroyer/gradle-errorprone-plugin-v0.0.x

Jcenter/central availability

gabrielittner opened this issue · 6 comments

tbroyer commented

I switched to plugins.gradle.org, and they automatically redirect to JCenter when they don't host it themselves; so couldn't you just replace jcenter() with maven { url "https://plugins.gradle.org/m2/" } ?

Is there a specific reason you cannot use plugins.gradle.org?

gabrielittner commented

Sorry, forgot to answer.
We proxy everything through a private Nexus instance and proxying https://plugins.gradle.org/m2/ does not seem to work. So it would be nice to still have it available in central.

jaredsburrows commented

+1 jcenter

tbroyer commented

We too do proxy https://plugins.gradle.org/m2/ through Nexus at work, and it works like a charm.

There's apparently a caveat though: do not use the (incubating) new plugins {} syntax (see https://discuss.gradle.org/t/publish-plugin-and-sonatype-ossrh/9998/16), but you're probably not using it anyway.

Closing for now; can reopen if someone comes with a compelling use case.

chintootech commented

Gradle 3.1 can't seem to find 0.0.8,

  > Could not resolve net.ltgt.gradle:gradle-errorprone-plugin:0.0.8.
     > Could not get resource 'https://plugins.gradle.org/m2/net/ltgt/gradle/gradle-errorprone-plugin/0.0.8/gradle-errorprone-plugin-0.0.8.pom'.
        > Could not HEAD 'https://plugins.gradle.org/m2/net/ltgt/gradle/gradle-errorprone-plugin/0.0.8/gradle-errorprone-plugin-0.0.8.pom'.
           > org.apache.http.client.ClientProtocolException (no error message)
  > Could not resolve net.ltgt.gradle:gradle-errorprone-plugin:0.0.8.
     > Could not get resource 'https://plugins.gradle.org/m2/net/ltgt/gradle/gradle-errorprone-plugin/0.0.8/gradle-errorprone-plugin-0.0.8.pom'.
        > Could not HEAD 'https://plugins.gradle.org/m2/net/ltgt/gradle/gradle-errorprone-plugin/0.0.8/gradle-errorprone-plugin-0.0.8.pom'.
           > org.apache.http.client.ClientProtocolException (no error message)
jaredsburrows commented

@chintootech This must be on your end. I have many github projects that use this plugin just fine.