- This topic has 28 replies, 6 voices, and was last updated 15 years, 4 months ago by
.
-
Posts
-
I haven’t used the all-in-one-installer for 3 reasons. One (minor) thing is that it is nice for new installs here that we don’t have to wait for a 600mb download. Another thing is that I don’t need or want the packaged jdk. Most important of all however is that pulse simply doesn’t work for me. It hasnt’ in the past and it hasn’t gotten better. I get the following popup:
An unexpected failure occurred inializing the installer.
java.lang.NoClassDefFoundError: com.genuitec.pulse2.common.http.PulseCommunications
and the following terminal output:
Architecture: Linux/x86_64
Redirecting System.out and System.err to /home/jasper.floor/Genuitec/Common/logs/installer-console.log
Could not redirect System.out and System.err!!!
8-Jan-09 12:16:19 PM com.oaklandsw.http.GlobalState <init>
INFO: Oakland Software Java HTTP Client 2.5.1Now I neither need nor want pulse on my computer. I have Synaptic or for eclipse the internal update manager. The problems with pulse are doubtlessly related to my setup and I don’t expect you to support all possible architectures. I hope pulse isn’t your ultimate solution for distribution because I really have no desire to spend time on Pulse.
I will try reinstalling Ganymede classic not using the archived update but iinstead the eclipse update manager.
@support-nipun wrote:
jasper.floor,
I would suggest you setup MyEclipse using the 64 bit All in One installer and test this again. ME was not supported officially on the 64 bit OS till we came out with the 64 bit All in One installer..For reference, I also installed Eclipse 3.4/MyEclipse 7.0/JDK6u11 on Lenny 64 bits using the archived update and experienced no problems.
Jasper’s implicit suggestion to use apt-get seems interesting though. Is there someway you can setup a repository for Debian (including Ubuntu) instead of Pulse?
I mainly see 2 problems with pulse:
The first problem is that it doesn’t work. This is major really.
The second problem is that even if Pulse would work, it introduces yet another update manager. On Linux it’s already bad enough that Eclipse came with its own update/package-like management system. Yet another one to deal with is perhaps not something that all users are happy with.I’m also interested in learning what the all-in-one installer would possibly do differently from the archived update site.
jasper.floor,
I checked with the dev team and they have asked me to point you to the archive update installer and that should work for you. You can grab the archive update for the download page.
http://www.myeclipseide.com/modules.php?name=Downloads&file=dl_options@support-nipun wrote:
jasper.floor,
I checked with the dev team and they have asked me to point you to the archive update installer and that should work for you.Didn’t he already tried that?
See this:
@jasper.floor wrote:
I installed MyEclipse using an archived update from within Eclipse.
henk,
Thank for pointing this out. My bad.
@jasper.floor – Ideally the archive update site installer should work for you. Did you run into the pulse errors mentioned above with pulse 2?It seems to have stabilised to about 1 memory error a day, which is workable if annoying. I have never gotten pulse to work in any version but I have tried it. I’m not against Pulse as such I just don’t need yet another package manager.
I am using my old project workspace, but the problem does persist if I do a clean workspace and a new checkout.
Maybe you could setup another copy of MyEclipse using the 64 bit all in one installer and evaluate it when you get time. We have improved the pluse experience and hopefully you will not run into the errors you were facing earlier.
FYI…I get the same low memory error messages using the 64 bit version under fedora 10, which I installed using the 64 bit all in one installer. I found the frequency of the low memory messages seems to be related to the number of projects (4-5) and size of projects (as large as 600 files) currently open which never occurred under earlier versions of MyEclipse (6.x) running the 32 bit version on the same 64 bit system with 4G of memory. Seems to be memory management issues with the 64 bit release…the heap size climbs to over 400M during the initial work space project build process which usually generates the low memory message unless I close all but one of the projects.
Can you guys turn on the heap space monitor (it’s under Window > Prefs > General) and restart and watch the monitor and see what operations cause it to spike. That will help us in resolving this issue.
I have quite incidentally been working in a workspace with only two projects open, whereas before I was working with workspaces with 8 or more projects. That does seem to have a positive effect on the memory management. I still have the bigger workspaces and so I may meet this problem again, especially around release time. I will monitor the heap size however and let you know what I find.
