updating of Gradle dependencies or initializing makes Eclipse unusable about eclipse-integration-gradle HOT 5 CLOSED

Then when network connection timeout, then even close Eclipse correct becomes problem.

Why just to start gradle potentially long running task in external shell.
Please give option for that so that new users do not experience Eclipse hanging.

from eclipse-integration-gradle.

after restart the same operation starts again.

This Eclipse workspace is almost broken. I rename project folder to kill Eclipse.

After Eclipse restart, and renaming the project back I get

I wonder why Eclipse wants to get gradle 1.5 when I have 1.9 installed on PATH ?

from eclipse-integration-gradle.

I wonder why Eclipse wants to get gradle 1.5 when I have 1.9 installed on PATH ?

It uses the default that the embedded Gradle tooling API chooses. You can override the default via the gradle preferences page in Eclipse.

Generally Eclipse does not pick up things from your PATH variable. You have to tell Eclipse via preferences pages which versions of a runtime to use.

Is recommendation to build first outside of Eclipse?

That would probably help since a lot of information will be cached by gradle making the next build much faster. However it will still need a decent network connection because even though dependencies are cached locally I think gradle will still verify them again (which is faster than downloading them but still needs network access).

from eclipse-integration-gradle.

Thank you, Kris

from eclipse-integration-gradle.

I'm closing his issue.

This is really a known issue and there isn't much that can be done without major architectural changes to how the tools work.

I do appreciate however you raising the issue. You are not the first to complain about this kind of problem and its something we'll keep in mind towards the future.

from eclipse-integration-gradle.