>
> What would you hope to gain from this, compared to a smart Gradle cache?
>
There are 3 benefits.
1, The company cache is unavailable. Ok, this is not a great reason,
but does happen, usually becuase the machine runs out of disk space.
2, Less network access
3, Portability, with a local cache on my laptop, should I leave to
work elsewhere I would generally have all the artifacts required.
The third reason was the winner for me. When I worked off site, I
found that even though I could sync the local project with the SCM
(git or svn etc) over the vpn, ie small updates over slow connection,
I have found that sometimes a new or updated project dependency was
added and would fail my build, and pulling all the artifacts over a
slow connection would be frustrating and time consuming to say the
least.
Sometimes I would have to checkout and build that dependent project,
which in turn would mean I would need to locate all the other
dependencies that I would not normally have on my local cache.
With a local Artifactory I found that I would mostly have everything
required on my machine.
WIth a distributed cache, where all updates that get published to a
company repo, are push to my local repo automatically, I would never
have an issue of getting the required dependencies.
-Mike
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
