Eclipse plugin not coping with Scala+Plugin rebuild

On Sun, Apr 25, 2010 at 3:49 AM, Ben Hutchison wrote:
> I have the Scala compiler/library/plugin src checked out as Eclipse
> projects in the configuration described on the EPFL wiki.

This is really a question for scala-ide-dev ... sign up here,

http://groups.google.com/group/scala-ide-dev

if you haven't already.

Cheers,

Miles

If you run eclipsec.exe, so you can see eclipse's standard out, it tells you what it's building.

On Sat, Apr 24, 2010 at 10:49 PM, Ben Hutchison <brhutchison@gmail.com> wrote:

I have the Scala compiler/library/plugin src checked out as Eclipse
projects in the configuration described on the EPFL wiki.

At 11:55 I did a Svn update of all four projects. Since then (45
minutes now) my CPU has been running at 100%, resuming soon after a
hard restart of Eclipse.

What should I do? How can I move forward, or make any informed
decision as to whether the system is in infinite loop?

Problems

1. I feel the SDT does not give the user sufficient feedback as to
what's happening. Progress view shows "Building workspace 76%", it has
shown that for the last 10 minutes, when it updated from 75%. I want a
way to see more detail: building what??.

2. No throttling of CPU consumption. When SDT builds, it sucks all
available CPU without respite. The UI becomes unresponsive, for
minutes at a time or indefinitely. I'd like a way to pause every
minute or so, even if there is work remaining to do, so I can at least
exit eclipse or cancel the builder.

Huge build times and massive CPU demand seem to be part of working
with Scala. I think the SDT design needs to be "hardened" to better
tolerate and manage these problems, or it will be unusable for large
projects.

-Ben