Hi Rickard, 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 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). Regards, Andrew Schetinin On Mon, Mar 28, 2011 at 8:00 AM, Rickard Öberg <[email protected]>wrote: > Hi, > > We at Qi4j recently switched over to use Gradle for our builds. Overall it > is working quite well, but I'm having a weird problem that I don't know how > to fix. > > If I do for example "gradlew idea" to generate IDEA modules/projects I can > see that the process is quite slow. I connected to the process using > VisualVM, and could see the CPU usage being in the range of 0.5%-8%. So, my > performance issues is not so much that it's slow, it's that the CPU doesn't > seem to be used at all. This seems to be happening with most targets by the > way. > > Has anyone seen this? How to fix? Any settings I missed? I wouldn't mind > the CPU usage being closer to 100%, if possible. > > thanks, Rickard > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- -- Andrew Schetinin
