In fact I'm going back to #655 because #657 with its integrated JRE was quite unusable for me too (no Javadoc and all the other annoyances).

I cannot believe that they are going to deliver this mess as a final release. Do they really expect their customers to tweak around with the startupfile just to make all the goodies work, that worked by default in all the builds up to #655?

Since #657 IDEA's JRE is configured as the default JDK, named "1.4.1",which is in fact isn't a real JDK (missing javadoc generator, etc).

But then I found out that you just need to configure and use a real JDK inProject Properties and name it "1.4.1". From then on, the supplied JRE onlyserves as IDEA's runtime environment. Any other needed component is usedfrom the configured JDK.

Maybe this is not optimal, but at least more convenient than having to tweakstartup files.

This really should be cross-posted in the "Announcements (EAP)" forum. That is where I always go for information on the latest build. If there is a reason that people shouldn't use a build that was previously released, you should make an announcement that informs everyone - not just those following this particular thread.

There is nothing to forgive - we're all human, mistakes happen. IDEA is a great tool, and so far we've all been using the early-release without any real problems. That we've got this far without a cock-up is a testament to the skill of the IDEA team. --Bryan

...657 was a diplomatic cock-up and 658 a technical disaster. Having been able to walk on water in the past it looks like the boys (and girls) at IntelliJ could do to sit back and take a breath. The pressures of hitting a release dead-line appears to have knocked them off their otherwise impeccable stride.