2.42 plugin marker artifact not available at Google maven
See original GitHub issueHi,
in the past we only used google()
and gradlePluginPortal()
as maven repositories for our plugin configuration in Gradle. With 2.41 we switched to the new com.google.dagger.hilt.android
plugin ID (which worked fine). Now after updating to 2.42 we were forced to add mavenCentral()
as a plugin repository.
So I guess the plugin marker artifact is missing in Google Maven?
Current behaviour:
Using the com.google.dagger.hilt.android
plugin ID requires to add/use mavenCentral()
as repository.
Expected behaviour:
Using the com.google.dagger.hilt.android
plugin ID should work with only google()
as repository (same as 2.41)
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Plugin [id: 'dagger.hilt.android.plugin'] was not found in any of ...
Due to the above missing Plugin Marker Artifacts you need to manually resolve the plugin using Plugin Resolution Rules at settings.gradle by ...
Read more >How can I customize the pom of the Plugin Marker Artifacts
In a maven repository the Plugin Marker is a pom file with these coordinates: groupId: plugin.id artifactId: plugin.id.gradle.plugin ...
Read more >Maven repository undeterministically returns Not Found errors
First, we disabled the publishing of "plugin marker artifacts". These artifacts merely reference the main artifact, which actually contains the ...
Read more >Untitled
Initial packaging - Add requires on OpenJDK - Update README - Add missing ... Added symlinks to lucene3 artifacts - Add missing BR...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the detailed explanation and investigation @tbroyer! I’ll close this now since there is no action item for us.
Fwiw, I confirm that this is a problem with JCenter. Currently, partly because of JCenter’s unreliability, Gradle, Inc. has setup a cache on their side; so when you try to resolve some artifact from plugins.gradle.org/m2, here’s what happens:
The problem here is that JCenter currently seems to answer with a 403.
Try for yourself:
And currently, at step 2:
Now try it out with 2.41, you get the POM, because it was cached already.
My rule of thumb, because of the unreliability of JCenter (not only in terms of availability, I caught them rewriting the POMs from time to time, breaking checksum verifications), is to always
gradlePluginPortal()
last, and addmavenCentral()
: if it’s not in gradlePluginPortal, it has good chances to be in mavenCentral, unless you rely on an old artifact that was only available in JCenter before it became readonly, and then you’re dependent on JCenter’s availability. Presence of artifacts in JCenter only is probably the only reason Gradle cannot break that dependency, which is why they setup an additional cache for when JCenter is unavailable.TL;DR: