Hi Andrew! Thanks for the suggestions!
On 3/28/11 16:50 , Andrew Schetinin wrote:
This happens usually due to Gradle (or, more correctly, Ivy) searching for many-many dependencies. As I've learned, it's less of a Gradle problem, and more like a design issue (a feature, not a bug) with Maven dependencies. There are a few ways of handling it: 1. a trick - there is an Ivy setting that disables those lengthy lookups gradle -Divy.cache.ttl.default=eternal build
Unfortunately this didn't make any difference at all, so it's gotta be something else. I tried with both "idea" and "build" targets, and they seemed as usual, i.e. CPU usage was very low.
2. a better solution (we're using now) is installing a company artifact repository (Nexus or Artifactory - both easy to install and use) on a server which is fast to access (may be an Intranet server, or even a local server - in our case it sits on a domestic hosting and it works just fine).
Unfortunately we're a distributed OpenSource project, and so there's no "local" (I work from home personally).
Hopefully there are other ways of dealing with this :-( /Rickard --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
