I don't think this issue should be considered "resolved". There is still much work to do here to provide real progress information.

Lacking:

• few messages provided in progress reporting, many times there is no progress being reported for minutes at a time. In this time IDE UI looks completely stuck.
• no "percentage" indication of progress.

The percentage doesn't need to be very precise, just give some idea that something is happening and there is an end point. I think it is perfectly ok if the bar slows down and speeds up. It's even ok to get stuck for a bit, just not minutes at a time.

Example: I was trying spring-data-mapping project from github.

• checkout from git
• update wrapper to M3
• on commandline build with "./gradlew assemble"
• then try to import the projects in STS/Eclipse

Building the sekeletal model gets completely stuck with no progress nor any output in the console for a very long time (3 minutes?).

With the same project... updating the classpath container also gets stuck for a long time without any progress.
(I seea bunch of "downloading" messages first, but after those stop it freezes up completely. (I'm typing this while waiting, its been sitting there for 2 minutes already without any sign of progress.

One concrete improvement that can be made is reporting the downloading of "pom" files. Right now only seeing the downloading of .jars in the progress reporting, but a long time is being spent downloading poms in most project's during "Configuring projects". This is printed to console, but not shown in the progress messages.

It's still sitting there... no progress for more than 10 minutes now. Also I really wonder what the hell it is doing, since my CPU is 90% idle.

@Kris, let's add new, more specific, issues for making progress reporting work better.

I've added GRADLE-1540 and GRADLE-1541 based on your comments.