I'm using Eclipse Juno with gradle1.4 set in the preferences and an ivy repository. I have proxy settings in a gradle.properties file. The project builds successfully on the command line in a couple of seconds. The project is basic, it doesn't contain sub-projects but it takes over 20 hours to populate the model & build. There are 40 dependent libraries, but I have transitive set to false for each and I have a fixed version specified for each jar. I'm just converting the projects to gradle from ant, so don't want to remove jar files already included in the project.

Since the request fails, Gradle doesn't cache this result, and tries again the next time you run the build. (Repository errors like this are treated as transient).

So that explains what's going wrong. But I don't understand why this doesn't affect you when running Gradle from the command-line. A few things to might help:

The output of 'gradle --debug eclipse'. Only the output as far as resolving the hibernate-annotations sources jar is necessary. - The output of 'gradle --debug --refresh-dependencies eclipse', as above.

I've managed to figure out what the problem is but not why it's happening. The dependencies aren't resolved when the proxy server is being used. So when I tried to build from the command line it FAILED!

When I removed the proxy settings from the command line everything worked!

But getting back to eclipse... it's still fails despite not having proxy settings set! I've cleaned/deleted everything I could think off gradle.properties files, .metadata directory, .gradle directories, deleted the cache, remove all JVM arguments under Windows->Preferences->Gradle. Checked my environment system path, proxy settings aren't set anywhere.

Yet when I run Gradle->RefreshAll in eclipse. It finds & sets the proxy settings which is why it is failing.

Both of the following builds were done without the gradle.properties, so no proxy settings I've attached 2 log files,