I always like to backup project dependencies myself in case they can't be resolved due to a down website or because certain versions aren't available for download any more.Should I trust the maven central repository to be up and running when I try to build my project in 2020? Or should I backup dependencies manual?If I should backup manual, then where does gradle store the downloaded dependencies? Or does gradle come with an build in solution for this?
Should I backup gradle dependencies to git?
version control;git;backups;gradle
For my important projects I try to make sure I have a backup of the following:Dependencies for all releases.Installation packages and instructions for all important tooling, such as IDE and compilers (used to build the application).Saving them in your version control system is not the right thing to, as it is not created to store large blobs. Instead I use backuped project drive.Automated solution with NexusFor maven central (and comparable) dependencies you also have another option. I have done this in the past with Maven, but it can also be done with Gradle. The solution is to run Nexus as a cache. Instead of directly downloading your dependencies from Maven Central, you tell Gradle to download from Nexus, which in turn can be set up to download dependencies from a central repository, caching the artifacts in the process.  As noted by Sleske in the comments: Make sure that the cache is not automatically cleaned by Nexus. Also the following will have the added benefit that other local users will be able to download dependencies locally (so possibly quicker). 