For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 4 replies, 4 voices, and was last updated 16 years, 7 months ago by
.
-
Posts
-
I’m a long time MyEclipse user who recently moved to a Linux 64-bit environment. In the “old days” there was a manual install for MyEclipse. I could use it in a 64 bit Solaris/SPARC environment, a Windows environment, or my Solaris x86 environment. MyEclipse worked the same everywhere. Now there is obviously native code that removes the benefits of Java from MyEclipse. I’m sure that there was a good reason but it broke the model that let me pick my dev environment.
Can’t there be a lower featured manual install? I don’t care about GUI design. I care about things that are J2EE related. As it is I have to use the 32 bit MyEclipse in my Linux environment now or, as I’ve been doing recently, just using the J2EE version of Eclipse. It isn’t as good but I can now pull a 2.5GB JVM into Eclipse.
Honestly, 7.0 has made me rethink my need for MyEclipse. If I’m tied to particular platforms I may as well just use Eclipse. I’d gladly double my yearly subscription price (and bring MyEclipse to the multi-platform team I manage) if I could have more portability.
What do you say MyEclipse folks – can you dump the native code if the customer prefers that?
stdunbar,
Actually this is exactly why we provide the Archived Update Site (download #4) on the download page. This is basically the manual install, just “update site manager friendly” — so it’s easier to use.
Did you give this a try?
I agree with the above posters one of the great things about myeclipse before 7.x was the ease at which one can manually install it on their system. What I see happening now is that maybe your trying to fix something that is not broken, or maybe get a little more fancy with the installation process which as is the case now actually causes MORE problems than solves. I’d rather see the myeclipse team spend resources adding new features (ahem *SEAM*, *FACELETS SUPPORT*, *GROOVY*, *MDA*, etc) and FIXING critical bugs than worry about how the fancy control panel on myeclipse looks. I’m thinking the amount of resources you spent on that control panel you could have easily added or improved native facelets support, or improve the preview rendering of the jsf editor.
