Hans,
On 3-Jun-08, at 11:39 PM, Hans Dockter wrote:
On Jun 3, 2008, at 10:54 PM, Jayson Minard wrote:
Hey simple question...
What is the best way to direct IVY within Gradle as to where you
want it to download dependencies (instead of to $home/.ivy dirs)?
In 0.1.4 there is a bug that Gradle downloads dependencies and
descriptor files into .ivy2/cache instead of .gradle/cache. This is
fixed in svn.
The default location is the Gradle user home dir. You can change the
gradle user home dir but not the fact that gradle user home is used
for the cache right now. We could improve this easily.
What is your use case for having a different location?
First it allows projects to be isolated from each other in a
guaranteed way (rather than we hope that two repositories don't return
two different versions of the same JAR and mess up the cache).
Second, I would like the build to be able to leave behind dependency
artifacts (like you might with Ivy) within your tree so that you can
freeze them locally if you want. I.e. have a local resolver ahead of
a remote resolver and have the remote resolver pull to the same dir as
the local resolver. Allows you to cache and survive internet
disconnects, etc. It is also nicer to wire the project up to have
its dependencies in a known place for the IDE's, makes the projects
portable so you can zip them up and send them off if you wanted. By
convention it can default to the home dir, but that should be able to
be overridden to directories such as ./lib
I could submit a patch for this, but I'm trying to get in deeper on
the plugin side first which has plenty of tricky areas to tie into
IntelliJ as it is :)
--j
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
