Backup Cache and Ivy Cache
The ivy cache is basically a folder where ivy stores artifacts and configurations. If not configured differently , it can be found in UserHome / .ivy2
The ivy cache consists of a permission cache and a storage cache.
The repository cache contains artifacts from the repository that were loaded with ivy. It caches the repository, so ivy will not need to request the repository every time it tries to allow / load the artifact. If he finds a suitable artifact in the repository cache, he will not request the repository. Thus, cost savings on the repository request. If and how the cache is used, it is a little more complicated and depends on dependencies / configuration.
The permission cache is a collection of ivy files that show ivy how the artifact was resolved (loaded).
"Ivy repository", unlike my regular SCM, which is a server with SVN
A repository in the ivy world is a location containing artifact files (jar). It can be a local file system or a web server. It does not have a version control system. Each version of the artifact is contained in a separate folder. You cannot commit artifacts; you simply add them to the file system. See terminology
org\artifact\version1\artifact.jar org\artifact\version2\artifact.jar
Access to the repository is carried out using resolver , which must know the location of the repository.
From doc to cache:
Cache types An Ivy cache is composed of two different parts: the repository cache The repository cache is where Ivy stores data downloaded from module repositories, along with some meta information concerning these artifacts, like their original location. This part of the cache can be shared if you use a well suited lock strategy. the resolution cache This part of the cache is used to store resolution data, which is used by Ivy to reuse the results of a resolve process. This part of the cache is overwritten each time a new resolve is performed, and should never be used by multiple processes at the same time. While there is always only one resolution cache, you can define multiple repository caches, each resolver being able to use a separate cache.