# bintray Published articles for bintray. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Plugin Portal Outage Followup DevFeed: [Plugin Portal Outage Followup]() Original publisher: [Read original article]() Author: Sterling Greene Published: 2023-06-28T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Maven](), [Library]() Tags: [bintray](), [blog-post](), [dependencies](), [gradle](), [gradle-plugin](), [jfrog](), [libraries](), [maven-central](), [outage](), [plugin]() ### AI overview This follow-up explains how an unannounced JCenter change on June 23, 2023 caused Gradle users to experience failures resolving artifacts through the Gradle Plugin Portal. It describes the impact on plugin builds, missing artifacts and transitive dependencies, recovery options, and plans to reduce reliance on JCenter. ### Source excerpt ℹ Update on July 15, 2024 See our recent blog post for up-to-date information about the Plugin Portal and JCenter. On June 23rd, 2023, at 9:00 UTC, Gradle users started experiencing issues resolving artifacts from the Gradle Plugin Portal because of changes to artifacts hosted on JCenter by JFrog. JCenter stopped serving files directly and redirected all requests to Maven Central. This was an unannounced change. We contacted JFrog, and they replied it was a test and they would revert back to having JCenter serve artifacts. Around 18:30 UTC, JCenter returned to normal behavior. This post describes the effect this outage had on builds, ways to recover from similar outages, and what we will do to eliminate the dependency on JCenter in the future. Users still directly using JCenter should also refer to our original blog post about the shutdown of JCenter on Gradle builds in general. Effects on Gradle plugins usage in builds When JFrog stopped serving artifacts from JCenter, all requests were redirected to Maven Central. This can impact builds in different ways. In this blog post, we focus on the resolution of Gradle plugins from the Plugin Portal. Background information The Plugin Portal only hosts artifacts related to Gradle plugins. The Plugin Portal redirects Gradle builds to JCenter to resolve transitive dependencies required by plugins. Some of these transitive dependencies are hosted by JCenter and some are mirrored from Maven Central. Additionally, some very old versions of Gradle plugins are also hosted on JCenter. This is because they were historically hosted on JFrog's Bintray service. Following Bintray's shutdown in May 2021, we removed the Plugin Portal's integration with Bintray, but we kept redirecting to JCenter for those artifacts because JFrog committed to keeping JCenter read-only indefinitely. When changes are made to JCenter, the Plugin Portal may no longer serve some artifacts or serve different artifacts. Missing artifacts Any artifacts only avail ## Deploy your internal libraries on Github DevFeed: [Deploy your internal libraries on Github]() Original publisher: [Read original article]() Author: Romain Boisselle Published: 2021-04-27T05:20:12Z Content type: tutorial Language: en Sources: [Kodein Koders - Medium]() Topics: [GitHub](), [Gradle](), [Maven Central]() Tags: [bintray](), [build](), [dependency](), [github](), [gradle](), [gradle-plugin](), [how-to](), [http](), [maven](), [maven-central](), [open-source](), [plugin](), [releases](), [repo](), [tutorial]() ### AI overview This tutorial explains how to publish internal libraries or early-access releases outside Maven Central by hosting Gradle plugin releases in a GitHub repository branch and serving them over HTTP. It also explains why the authors chose this approach instead of GitHub Packages, which requires authentication even for public packages. ### Source excerpt In a previous tutorial, I explain how to configure and deploy your libraries to Maven Central. But, there are some libraries that that do... Continue reading on Kodein Koders " ## JCenter Shutdown Impact on Gradle Builds DevFeed: [JCenter Shutdown Impact on Gradle Builds]() Original publisher: [Read original article]() Author: Sterling Greene Published: 2021-02-22T05:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Maven](), [Security](), [Git](), [GitHub]() Tags: [bintray](), [build](), [central](), [dependencies](), [documentation](), [github](), [gradle](), [jfrog](), [maven-central](), [mirror](), [packages](), [pipelines](), [release](), [update]() ### 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 ## Publishing Android libraries to MavenCentral in 2021 DevFeed: [Publishing Android libraries to MavenCentral in 2021]() Original publisher: [Read original article]() Author: Márton Braun Published: 2021-02-04T16:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Library](), [Maven](), [Gradle](), [GitHub Actions](), [API]() Tags: [android](), [bintray](), [ci](), [github](), [github-actions](), [gradle](), [guide](), [how-to](), [integrity](), [libraries](), [maven-repository](), [mavencentral](), [release](), [repositories](), [signing](), [sonatype](), [tutorials]() ### AI overview A step-by-step, updated guide to publishing Android and other libraries to MavenCentral in 2021. It covers Gradle publishing, GPG signing, Sonatype infrastructure, Maven publishing plugins, and GitHub Actions CI, with context on JitPack and JCenter. ### Source excerpt MavenCentral is the place to be for Android libraries, but publishing there is no easy task. With JCenter going away soon, this problem is more timely than ever. Here's the step-by-step guide on how to do it. ## Migrating away from JCenter DevFeed: [Migrating away from JCenter]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2021-02-04T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Gradle](), [Maven](), [Maven Central](), [Jfrog]() Tags: [android](), [bintray](), [blogs](), [dependencies](), [gradle](), [guide](), [how-to](), [jcenter](), [jfrog](), [library](), [maven](), [maven-central](), [migrate](), [repository](), [transitive-dependencies]() ### AI overview A practical guide to migrating Gradle dependencies and published artifacts away from Bintray/JCenter after JFrog announced the repository shutdown. It explains replacing JCenter with Maven Central, testing clean builds, and restricting remaining dependencies to explicit repository declarations. ### Source excerpt This week JFrog - out of nowhere - announced to completely remove their Maven repository. Since they'll pull it offline already by May 2021 (!!!) it's time to urgently migrate away.