2009/6/29 Stefan Flemming
<stefan@...>
The only thing I realized was, that activating Java SE took about 3 minutes on my MacBookPro. Did someone else realize this?
It is not as bad since it is only called the first time, when I use it but maybe a small additional message would help users to recognize that this is no freeze?
I left activating NB6.7 running overnight showing activating Java SE. It was still doing it 7 hours later. Not a good start. Two further restarts (each with exceptions
http://www.netbeans.org/issues/show_bug.cgi?id=123559), and then a project scanning using >100% cpu (on linux with dual core) for >30mins (before I killed it).
Hmmm. All I did was open a Maven Java project in a newly installed IDE. Something it should be able to handle easily.
Regards
Neil
