I actually discovered a better solution to this by setting GRADLE_USER_HOME to a global directory in system wide environment properties. This allows other users to reuse the dependencies another user on the machine may have already cached.
Ideal for an XP shop to prevent a full download of large deps whenever another pair logs into a machine. :) Thanks, James On Mon, May 2, 2011 at 4:38 PM, James Carr <[email protected]> wrote: > Yeah, I suppose I could just create an alias on the machines so that > gradle resolves to gradle -g. > > > Thanks, > James > > > On Mon, May 2, 2011 at 4:31 PM, Rene Groeschke <[email protected]> wrote: >> Hi james, >> you can use the -g command line option, can't you? >> regards, >> René >> >> Am 02.05.11 23:30, schrieb James Carr: >>> >>> Hi, >>> >>> Is there a way to configure a common location to store gradle's >>> resolved artifacts? It'd be nice to cache dependencies in a common >>> location besides the user's directory as at our workplace different >>> people log into machines quite often. >>> >>> >>> Thanks, >>> James >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >> >> >> -- >> ----------------------- >> regards René >> >> rene groeschke >> http://www.breskeby.com >> @breskeby >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
