All geek questions in one place

Any serious problems with Helios?

I just saw that a new major release ( 3.6 Helios ) eclipse is available for download. I want to try, but before that I want to know if anyone has serious problems.

I want to determine if I can try it or not, since my project setup is complicated and easily takes 2, 3 hours in normal mode; I do not want to risk.

+4
source share
8 answers

No major issues.

The main problems that I saw are platform specific, for example, a crash in Ubuntu .
Slight differences are noted in this post.

As usual, I always prefer a full installation of Eclipse next to the ones I already have.
And for the main update, I like to recreate the workspace intended for this version, just to be safe.
So my old release of Eclipse still has its own workspace, fully functional.
I also test plugins in both versions using the shared unpack folder .

+3
source

Yes, I am having a serious problem with helios, but only in the context of WTP. If you are working with WTP, you should immediately upgrade to WTP-M-3.2.1 . This should fix the deployment hotspot problem (republishing to the server). Problem with eclipse error .

+2
source

The most unpleasant thing for me was how the j2ee projects were configured: there are no more j2ee dependencies, and at first glance it is not obvious that you need to use the resource assembly (but this will not hold the Internet search for several minutes).

In addition, I did not have a real problem with the update: everything went smoothly, and I use plugins well under helios.

+1
source

Nothing special, but some of the suggestion functions are a bit erroneous:

  • sometimes instead of offering to create a method, it offers a listing and inserts the listing into Object
  • when generic interface methods exist, some of them are added as unrealized, even if they exist in the parent class.

These are two things that I met last week.

+1
source

On Windows, Helios really has a pretty critical conflict with the latest Oracle JDK patch (JDK 1.6 21 update):

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

Any version before this is normal.

+1
source

There is a problem with Helios and Oracle JVM 1.6.0 update 21 . Starting Eclipse starts the size of the pepper using a command-line parameter specific to Sun-jvm, but Oracle has changed the provider string from "Sun Microsystems" to "Oracle", and Eclipse now does not detect Sun-JVM, so it does not set the correct permenum size. A quick solution is to install permgen yourself in eclipse.ini.

+1
source

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

+1
source

In Windows 7, we recently switched to the 64-bit version of Helios. We saw a significant improvement in memory management with more Out Of Memory errors inside Eclipse. Much better results. But we have a big problem with the SVN and SVN Kit plugins, they constantly display Malformed Network data errors or Handshake failure errors when synchronizing with our repository in svn + ssh. It worked perfectly under 32 bits of Indigo or Galileo.

+1
source

Source: https://habr.com/ru/post/1315364/

More articles:


All Articles