4

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 problems.

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.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
Reddy
  • 8,737
  • 11
  • 55
  • 73

8 Answers8

3

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.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
2

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.

Christopher Klewes
  • 11,181
  • 18
  • 74
  • 102
1

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.

tonio
  • 10,355
  • 2
  • 46
  • 60
1

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.

Bozho
  • 588,226
  • 146
  • 1,060
  • 1,140
1

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.

soru
  • 5,464
  • 26
  • 30
1

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.

Peter Štibraný
  • 32,463
  • 16
  • 90
  • 116
1

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

nos
  • 223,662
  • 58
  • 417
  • 506
1

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.

Cédric NICOLAS
  • 1,006
  • 2
  • 12
  • 24
  • Comment on my own post : confused by the Eclipse names. We switch to Indigo 64 bits while we were Helios 32 bits. Then came our problem with SVN Kit in svn+ssh protocol constantly showing Handshake failed or Malformed Network data errors.. Sorry for confustion – Cédric NICOLAS Nov 21 '11 at 21:16