Any major problems with Helios?

I have just seen that new major release (3.6 Helios) of eclipse is available for download. I want to try it, but before that I want to know if anybody experienced any major pro开发者_JS百科blems.

I want to determine If I could try this or not, since my project setup is complex and easily takes 2, 3 hours normally; I don't want to take any risk.

No major issue sp far.

The main problems I have seen are platform specific, like this crash in Ubuntu.
Small differences are noted in this blog post.

As usual, I always prefer a full Eclipse installation beside the ones I already have.
And for major update, I like to recreate a workspace dedicated for that release, just to be on the safe side.
That way, my old Eclipse release still has its own workspace fully functional.
I also test the plugins in both version by using a shared dropins folder.

Yes i experienced a major problem with helios, but only in WTP context. If you work with WTP you should immediately update to WTP-M-3.2.1. This should fix the issue of taking up to a minute for hot deployment (re-publishing to the server). The eclipse bug issue.

The most disturbing thing for me was the way j2ee projects are configured: there is no more j2ee dependencies, and it is not obvious at the first glance to see you have to use resource assembly (but it does not resist a few minutes searching the web).

Apart for that, I had no real issue in updating: everything went smooth, and plugins I use work well under helios.

Nothing so major, but some suggestion features are a bit buggy:

• sometimes instead of suggesting to create a method, it suggest a cast, and inserts a cast to Object
• when there are interfaces methods with generics, some of them are added as unimplemented even though they exist in the parent class.

These are two things I encountered for the past week.

On Windows, Helios does appears to have a pretty critical conflict with the latest oracle JDK patch (JDK 1.6 update 21):

https://bugs.eclipse.org/bugs/show_bug.cgi?id=319514

Any version before that is ok.

There is an issue with Helios and Oracle JVM 1.6.0 update 21. Eclipse launcher sets permgen size using Sun-jvm-specific command line option, but Oracle changed vendor string from "Sun Microsystems" to "Oracle", and Eclipse now fails to detect Sun-JVM, so it is not setting right permgen size. Quick solution is to set permgen by yourself in eclipse.ini.

I'm getting incredibly slow autocomplete. The bug , with a workaround, is here https://bugs.eclipse.org/bugs/show_bug.cgi?id=317979

We switch to 64bits Helios under Windows 7 recently. We saw a major improvement in memory management no more Out Of Memory errors inside Eclipse. Much better performances as well. But we have a big issue with SVN and SVN Kit plugins they are constantly displaying Malformed Network data errors or Handshake fail errors when synchronising with our repository under svn+ssh. Was perfectly running under 32 bits Indigo or Galileo.