Apache 阿帕奇常春藤术语；含糊不清

我正在学习如何使用一种“蛮力”的方法，通过Ivy来增强我的构建，这种方法只是尝试启动和运行一些示例项目。我读过很多官方文件，也读过一些在线教程，但我还是被一些术语弄得喘不过气来，这些术语似乎用得含糊不清，模棱两可，或者以某种方式相互冲突。我只是想找一位经验丰富的常春藤鉴赏家帮我澄清一下这些术语

“分辨率”缓存与“存储库”缓存与“常春藤”缓存

“常春藤存储库”，与我的普通SCM不同，后者是运行SVN的服务器

这三种类型的缓存有什么区别？“常春藤知识库”和我的SVN有什么区别

感谢所有能帮忙的人

“分辨率”缓存与“存储库”缓存与“常春藤”缓存 ivy缓存基本上是一个文件夹，ivy在其中存储工件和配置。如果没有，可以在UserHome/.ivy2中找到

常春藤缓存由分辨率缓存和存储库缓存组成

存储库缓存包含由ivy下载的存储库中的工件。它正在缓存存储库，这样ivy就不需要在每次尝试解析/下载人工制品时查询存储库。如果它在存储库缓存中找到合适的工件，它将不会查询存储库。从而节省了查询存储库的成本。是否使用缓存以及如何使用缓存稍微复杂一些，这取决于依赖项/配置

解析缓存是常春藤特定文件的集合，这些文件告诉常春藤如何解析（下载）工件

“常春藤存储库”，与我的普通SCM不同，后者是运行SVN的服务器 常春藤世界中的存储库是一个包含工件（jar）文件的位置。这可以是本地文件系统或web服务器。它没有版本控制系统。工件的每个版本都包含在一个单独的文件夹中。您不能提交工件，只需将它们添加到文件系统。见

存储库是通过数据库访问的，数据库必须知道存储库的布局

从缓存上的

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.

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.