# JCenter Shutdown Impact on Gradle Builds

DevFeed: [JCenter Shutdown Impact on Gradle Builds](<https://devfeed.tech/articles/jcenter-shutdown-impact-on-gradle-builds-24662.md>)

Original publisher: [Read original article](<https://blog.gradle.org/jcenter-shutdown>)

Author: Sterling Greene

Published: 2021-02-22T05:00:00Z

Content type: article

Language: en

Sources: [The Gradle Blog](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Security](<https://devfeed.tech/topics/security.md>), [Git](<https://devfeed.tech/topics/git.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [bintray](<https://devfeed.tech/tags/bintray.md>), [build](<https://devfeed.tech/tags/build.md>), [central](<https://devfeed.tech/tags/central.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [github](<https://devfeed.tech/tags/github.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [jfrog](<https://devfeed.tech/tags/jfrog.md>), [maven-central](<https://devfeed.tech/tags/maven-central.md>), [mirror](<https://devfeed.tech/tags/mirror.md>), [packages](<https://devfeed.tech/tags/packages.md>), [pipelines](<https://devfeed.tech/tags/pipelines.md>), [release](<https://devfeed.tech/tags/release.md>), [update](<https://devfeed.tech/tags/update.md>)

## AI overview

This article explains how the shutdown of Bintray and JCenter could disrupt Gradle builds by affecting dependency resolution, plugin dependencies, and package publishing. It describes JCenter's relationship to Maven Central, notes that JCenter became read-only indefinitely, and recommends moving builds and publishing workflows to other repositories, with Maven Central becoming Gradle's default in new samples and init templates.

## Source excerpt

ℹ Update on July 15, 2024 See our recent blog post for up-to-date information about the Plugin Portal and JCenter. On February 3 2021, JFrog announced that they will be shutting down Bintray and JCenter. This post tells you what you need to know and do to avoid disruptions to your build pipelines. Your build may be affected by this shutdown in several ways: Gradle may not be able to download the dependencies used to compile, test or run your code. Gradle may not be able to download the dependencies used by plugins to configure your build. Gradle may no longer be able to publish your package to Bintray. Additionally, you should be aware of the security considerations when moving from one repository to another. UPDATE: JFrog has decided to keep JCenter as a read-only repository indefinitely. New package and versions are no longer accepted on JCenter. All Bintray services have been shutdown. Background JCenter is a central artifact repository, like Maven Central. Software projects use JCenter to distribute their software to other people. JCenter also serves as a mirror for Maven Central, so any dependencies available on Maven Central are also available on JCenter (but not vice versa). Bintray is a management layer that software projects use to publish and promote packages to JCenter. Bintray also allowed users to create public user-specific repositories that were isolated from JCenter. Both of these services are affected by the shutdown. Impact to builds By default, Gradle does not add an artifact repository to your project; however, Gradle does provide a convenient API for using the JCenter repository. The Gradle Build Init plugin produces build templates that use the JCenter repository to resolve dependencies. In many code examples and documentation, JCenter is used as an example repository. It's very likely that you have builds that rely on JCenter. We've found over a million Git repositories on GitHub that use JCenter with Gradle. To discourage new projects from u