![]() ![]() By trying Central first, you pay a small upfront cost for those artifacts coming from the Gradle Plugin Portal but on the other hand you will avoid redirects to JCenter and get a much more reliable build. (added ) Explicitly configure Central before the Gradle Plugin Portal: it's been a full year now that JCenter is read-only, meaning that there are good chances that all needed artifacts not provided by the Gradle Plugin Portal itself come from Central. Using gradlePluginPortal() means that any dependency (generally transitive dependencies from plugins) are resolved from JCenter, and there's no option to prevent this besides using repository content filtering (which means somehow duplicating here what you already have in your plugins blocks in build scripts), or declaring mavenCentral() before gradlePluginPortal(). add a specific HTTP header, so the Gradle Plugin Portal repository could reply with a 404 rather than 303. Or any other mechanism that could prevent using JCenter (that could be a flag passed to gradlePluginPortal() that would influence how it makes requests, e.g. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |