Import of Gradle IDE project with managed dependencies never finishes in Eclipse Kepler

[DKroot]

Our team is working on a project that used Gradle for builds, but IvyDE in Eclipse. I'm trying to migrate from IvyDE to Gradle IDE.

I've done it on Mac with Kepler, latest Gradle IDE and Groovy-Eclipse plug-ins. Everything went fine. I've committed all the changes, but when my teammates tried to update project on Windows, they all were stuck on "Update Gradle Classpath for Foo" / "Get model for 'Foo': Build" 52%.

Today I reproduced the issue on the fresh Kepler / Windows 32-bit.

Steps:

1. Install Grails IDE plug-in. (Tried it instead of Groovy-Eclipse)
2. Install Lombok (the project needs Lombok to compile)
3. Install Gradle IDE plug-in.
4. Import of existing project into workspace.
5. Stuck (Eclipse itself is responsive, but 'Update Gradle Classpath' never finishes

Couple of things I tried so far to no avail:

• Configure Gradle to use system installation of Gradle 1.6 (this is the version that we use) and default user's home (C:\Users\Bar.gradle)
• Resolve and cache all dependencies via command line: >gradle dependencies. It completed just fine.

[DKroot]

Forgot to mention: there is no related output in Eclipse Consoles or Eclipse Error Log whatsoever

[DKroot]

Next thing I tried to no avail:

• Remove Gradle container library in .classpath, open project and then try to enable Dependency Management

I'm running out of ideas.

[DKroot]

OK, these might be related: https://issuetracker.springsource.com/browse/STS-3419, https://issuetracker.springsource.com/browse/STS-3495 as our project does use Lombok. Now I have couple of more ideas: 1) try to disable Gradle daemon and 2) try to disable Lombok before Resolving Dependencies and then reenable it.

[bwmeier]

Disabling Lombok works, but is really annoying. I was unable to configure the Gradle daemon in any way that made the problem go away, though.

[kdvolder]

1. try to disable Gradle daemon

Not possible. The tooling API always uses the daemon. It can't be disabled.

[kdvolder]

Closing: this is a duplicate of STS issue linked above.

Also most likely its not really a bug in STS tooling but a problem that needs to be sorted out between gradle tooling API / daemon and lombok.