Running gradle eclipse for the Gradle project is pretty fast for me (around 20 seconds). So either we should repurpose this task to cover the problems reported by Chris Beams (for which I can't find an issue), or we should close it.

Test comment.

testing

Not sure what's going on with the status of this bug, but when I run gradle eclipse on a very small project it takes 2 mins, 30 seconds, making gradle completely unusable for a project. I'm using 1.0 M2 on Mac OS X 10.6.7 with Java 6.

Can you share the build script and/or project? The current status of this bug is "cannot reproduce".

I cannot share the project, but I'd be happy to share the build scripts (multi-project):

Parent project:

build.gradle:

subprojects {
apply plugin: 'java'
apply plugin: 'eclipse'
sourceCompatibility = 1.6

repositories

dependencies

version = '1.0'

jar

}

settings.gradle:

includeFlat 'core', 'data-common', 'data-riak', 'services'

The subprojects currently do not have any build.gradle files (as I was testing gradle moving from Maven). I've tried running gradle :data-common:eclipseClasspath and that alone takes 2:30, which is unbearably slow and unfortunately is going to force me to go back to Maven.

Here's my output from gradle -v:

------------------------------------------------------------
Gradle 1.0-milestone-2
------------------------------------------------------------

Gradle build time: Friday, 8 April 2011 03:06:53 PM EST
Groovy: 1.7.10
Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
Ivy: 2.2.0
JVM: 1.6.0_24 (Apple Inc. 19.1-b02-334)
OS: Mac OS X 10.6.7 x86_64

Please try it without the '+' at the dependencies and define the correct versions. Maybe the resolving of the dependencies take a long time.

Thanks Mathias. Yes, that sped things up, I'm now down to 12 seconds. I actually liked the thought of using + in the dependencies so it would pick up any dot releases that don't break anything, but I guess that's bad form anyway. Thanks!

Please vote for this issue: http://issues.gradle.org/browse/GRADLE-1333
And this issue can help to find the performance problems: http://issues.gradle.org/browse/GRADLE-1334

Thanks to many improvements, mainly in the dependency management front, the gradle eclipse is now swift. Therefore I allow myself to resolve this issue.