- This topic has 11 replies, 3 voices, and was last updated 14 years, 3 months ago by
.
-
Posts
-
———————————
Restoring a deleted post from my web browser cache
———————————I had always heard that (as someone quite clearly put it):
“Eclipse is built against Carbon (re: not Cocoa) and will only operate under a 32-bit JVM. On OS X, Java 6 is 64-bit only and therefore Eclipse cannot run under Java 6 until 64-bit SWT framework for Mac OS X is in place.”
However I just read (in a recent forum):
“Eclipse *does* now support Java 1.6, 64-bit, and cocoa on OS X. Cocoa builds have been available for over a year now, and since 3.5 they are production. So just grab the cocoa 32 or 64 (preferred) builds form download.eclipse.org and you’re golden.”
I tried getting MyEclipse 8.6 to run on Mac OS X 1.6 however it would instantly crash with EXIT 1 error code.
Unfortunately the latest TestNG plugin for Eclipse 5.13.0.3 appears to have been compiled with Java 6 and as such does not work anymore.
Hence my need to host MyEclipse on 1.6.X on Mac OS X. How is this done?????
–Nikolaos
———————————
Restoring a deleted post from my web browser cache
———————————Nikolaos,
First thanks for contacting us with your question. Let me start by saying I know I can help with this as I use a MacBook Pro every day and run MyEclipse 8.6 with Java 1.6 all the time.
Let me start by asking how did you install MyEclipse 8.6 on your Mac? If you tried downloading Eclipse then adding MyEclipse to it I’d highly recommend that you delete that installation and simply download our double-click installer for the Macintosh instead. You can get it on the MyEclipse download page as (I believe) the 4th download listed.
If you used another method to install or configure, can you please provide some details so we can determine what might be failing?
_________________
–Scott
MyEclipse SupportI had installed MyEclipse 8.5 with my primary JDK on my Mac pointing to 1.5.
All was well and recently I upgraded using the Control Center to MyEclipse 8.6. In the process of upgrading I also upgraded a plugin called TestNG to its latest version however it had been compiled with a minimum compliance level of 1.6.
Ergo I tried getting MyEclipse to run on 1.6 and failed with all of the following attempts:
1) I tried simply changing my current system wide JDK to 1.6 which was:
nikolaos (mac0) /System/Library/Frameworks/JavaVM.framework/Versions > ls -lrt
…
lrwxr-xr-x 1 root wheel 3 May 22 11:21 CurrentJDK -> 1.5To:
lrwxr-xr-x 1 root wheel 3 Aug 11 16:09 CurrentJDK -> 1.6However this didn’t do the trick as it appeared that MyEclipse had retained the 1.5 value from the install or something
2) I tried changing in:
/Library/Genuitec/MyEclipse\ 8.5/myeclipse.app/Contents/Info.plistFrom:
<!– to use a specific Java version (instead of the platform’s default) uncomment one of the following options:
<string>-vm</string><string>/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Commands/java</string>
<string>-vm</string><string>/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/java</string>
–>
<string>-keyring</string><string>~/.eclipse_keyring</string>To:
<!– to use a specific Java version (instead of the platform’s default) uncomment one of the following options:
<string>-vm</string><string>/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Commands/java</string>
<string>-vm</string><string>/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/java</string>
–>
<string>-vm</string><string>/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/java</string>
<string>-keyring</string><string>~/.eclipse_keyring</string>Which resulted in an immediate splash screen with Exit 1 error code (and a whole slew of settings)
3) I undid the above and added at the top in:
/Library/Genuitec/MyEclipse\ 8.5/myeclipse.app/Contents/MacOS/eclipse.ini-vm
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/javaWhich resulted in the same immediate splash screen with Exit 1 error code (and a whole slew of settings)
4) I undid the above and added at the top in:
/Library/Genuitec/MyEclipse\ 8.5/myeclipse.app/Contents/MacOS/myeclipse.ini-vm
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/javaWhich resulted in the same immediate splash screen with Exit 1 error code (and a whole slew of settings)
I know that there are some duplicate settings in myeclipse.ini and eclipse.ini w.r.t. heap settings and the like which I also would like to clear up but in any event here are the 2 ini files.
At this point it does not appear like a fresh install would resolve anything and keep in my mind if I did do one I have a lot installed and configured and I would need to setup a parallel install and somehow export and re-import the settings (I believe I saw an FAQ entry on how to do the latter but would appreciate any tips / assistance if necessary).
Ideas???
–Nikolaos
nikolaos (mac0) /Library/Genuitec/MyEclipse 8.5/myeclipse.app/Contents/MacOS > more < eclipse.ini
-showsplash
org.eclipse.platform
-vmargs
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Xms40m
-Xmx256m
-XX:MaxPermSize=256m
-Dorg.eclipse.swt.internal.carbon.smallFontsnikolaos (mac0) /Library/Genuitec/MyEclipse 8.5/myeclipse.app/Contents/MacOS > more < myeclipse.ini
-install
/Library/Genuitec/MyEclipse 8.5
-data
/Users/nikolaos2/home/sw/company
-startup
../../../../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
–launcher.library
../../../../Common/plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.200.v20090520-1835
-configuration
../../../configuration
-vmargs
-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
-Dorg.eclipse.swt.internal.carbon.smallFonts
-XstartOnFirstThreadNikolaos,
I’m bringing this response back from private email to the forum so hopefully this thread can benefit others. From your last email, here’s your current state and question:
I easily undid the 4 or so things that allowed me to test 1.6 but all
resulted in failure when I tried to start MyEclipse 8.6. At this point
MyEclipse launches fine and still uses 1.5 despite the fact that my
default JDK points to 1.6.So please let me know how I can switch MyEclipse to be hosted / run on
1.6. Feel free to simply reply to the forum post.First of all, it’s great that you’re back up and running with JDK 1.5 with MyEclipse. At least you have a working configuration again. Now, on with getting you an 8.6 install that uses JDK 1.6.
We do not recommend trying to manually change the launch JDK for MyEclipse (or any Eclipse-based product) due to the number of items that must be altered and the fact that it must all be done perfectly to work. So what I’d recommend is a very easy solution: allow our Custom Installer to do the work for you. Don’t worry, it won’t re-download MyEclipse; that fact that you already have 8.6 will be detected and the installer will simply write you out a new launch configuration that uses your default JDK, which is now 1.6. Simply follow these steps:
1) In your browser ensure that Java is enabled. The custom installer uses applets and I believe Java support is off by default in Safari.
2) Navigate to the MyEclipse download page and select the “Custom Installer” option.
3) Leave the default settings alone to get a full MyEclipse 8.6 installation and click the “Install >>” button
4) The next page will pause for a bit as Java loads (see little coffee cup icon) and then you’ll be prompted to allow our signed applet access to your computer. Please allow it. 🙂
5) Next, you’ll see some dialogs as we check your system state and look for updates. After that you’ll likely see a dialog that says you’ve already got this software installed. Your choices will be to “Launch existing installation” or “Install another copy of this software”. You want to “Install another copy of this software”. Again, the installer is smart and won’t need to download anything.
6) You’ll then be prompted to name your new installation and then pick where you want the configuration written. You cannot pick your existing name or configuration directory, but don’t worry, only a small set of launch files is written there.
7) When the installation completes you’ll have a MyEclipse 8.6 executable in the new directory that will be configured to use your default JDK, 1.6
8) Launch the new installation with an EMPTY workspace and verify that it’s “as you like it”
9) Open your existing workspace with the new install.Please let us know if you have any questions or problems.
So will all my preferences, configurations, plugins, etc… automatically get ported to the new installation?
If not, how can I restore my full configuration on the new install?
Thanks,
–Nikolaos
Scott,
I have good news and bad news. I followed your instructions and effortlessly “Installed another copy of the software” in less than 10 minutes. Great.
Except I am still running on 1.5.0_24 despite having 1.6.0 as my default JDK:
nikolaos (mac0) /Library/Genuitec > java -version
java version “1.6.0_20”
Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-9M3165)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode)AND when I check the installation details of MyEclipse:
*** Date:
Friday, August 13, 2010 5:58:38 o’clock PM EDT** System properties:
OS=MacOSX
OS version=10.5.8
Java version=1.5.0_24*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 8.6
Build id: 8.6-20100806*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 8.6
Build id: 8.6-20100806Eclipse startup command=-os
macosx
-ws
carbon
-arch
x86
-showsplash
-launcher
/Library/Genuitec/MyEclipse-8.6/myeclipse.app/Contents/MacOS/myeclipse
-name
Myeclipse
–launcher.library
/Library/Genuitec/MyEclipse-8.6/myeclipse.app/Contents/MacOS//../../../../Common/plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.200.v20090520-1835/eclipse_1206.so
-startup
/Library/Genuitec/MyEclipse-8.6/myeclipse.app/Contents/MacOS/../../../../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
/Library/Genuitec/MyEclipse-8.6
-configuration
../../../configuration
-keyring
/Users/nikolaos2/.eclipse_keyring
-consoleLog
-showlocation
-vm
/System/Library/Frameworks/JavaVM.frameworkScott,
I did a little deeper digging and found that the Installer copied my myeclipse.ini and eclipse.ini files verbatim and essentially cloned my entire configuration which is great / ideal except it never detected the 1.6.0 environment and still bombs if I try to configure the 1.6.0 JDK (despite 1.6.0 being the default JDK).
I feel like we have gone around in circles except that we have a configuration that we can muck with… .
–Nikolaos
Hi,
I’m currently still slogging along in a Windows 32 bit world here, but I thought I’d point out that the jdk6 issue you are seeing may not necessarily be specific to the Mac or to the 64 bit compier. I have encountered something sounding very similar when creating a new Web Project using MyEclipse For Spring 8.6 on 32-bit Windows, and I am told that this is not so much a ME4S specific thing as it is MyEclipse specific with web projects. Check these two problem reports and see if they look at all familiar:
http://www.myeclipseide.com/PNphpBB2-printview-t-24116-start-0.html
http://www.myeclipseide.com/PNphpBB2-printview-t-25585-start-0.htmlHi dav0,
Any issue with compliance level is unrelated to the issue that I am referring to… you can pick whatever JDK you like to compile with and set the compliance level appropriately.
What I would like to do is RUN MyEclipse on JDK 1.6 for a number of reasons including:
1) Any plugins that have been compiled with 1.6 and default compliance level (i.e. same as compiler version) or compliance level set to 1.6 will NOT RUN in MyEclipse because the 1.5 JVM that MyEclipse is running in will not be able to load classes that have their compliance level set to a 1.6 (minimum).
2) There are some performance improvements with 1.6 and 1.6 OSGI that someone claims can make Eclipse up to 4-5X faster… a claim no doubt… but any performance improvement would be extremely welcome.
3) Most people are happily developing with 1.6 as the default so why not bring the tools into alignment… again this is not generally an issue unless 1) happens to you AND as time goes by this will happen more and more often.
The real problem though on the Mac is the fact that 1.6 is exclusively 64-bit and as Apple is the defacto manufacturer there really isn’t much choice… this results in problems for things like SWT that have not long been available on 64-bit. As of Eclipse 3.5 this issue apparently has been resolved with 64-bit support being available.
On Windoze IIRC you can simply opt to use a 1.6 32-bit JDK and all is well to run MyEclipse so there isn’t any major issue there AFAIK.
In any event, appreciate your reply, and look forward to getting instructions to HOST MyEclipse on 1.6. I followed Scott’s instructions and now have a cloned configuration save plugins which appear to not have been installed but I am STILL on 1.5
–Nikolaos
@dav0 wrote:
Hi,
I’m currently still slogging along in a Windows 32 bit world here, but I thought I’d point out that the jdk6 issue you are seeing may not necessarily be specific to the Mac or to the 64 bit compier. I have encountered something sounding very similar when creating a new Web Project using MyEclipse For Spring 8.6 on 32-bit Windows, and I am told that this is not so much a ME4S specific thing as it is MyEclipse specific with web projects. Check these two problem reports and see if they look at all familiar:
http://www.myeclipseide.com/PNphpBB2-printview-t-24116-start-0.html
http://www.myeclipseide.com/PNphpBB2-printview-t-25585-start-0.htmlNikolaos,
This is interesting. Can you double-check the settings in /System/Library/Frameworks/JavaVM.framework/Versions
and see that they look like mine below?drwxr-xr-x 3 root wheel 102 Jul 20 2009 1.3.1 drwxr-xr-x 7 root wheel 238 Aug 14 2009 1.6.0 lrwxr-xr-x 1 root wheel 5 May 24 09:07 1.6 -> 1.6.0 lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.5.0 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.5 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.4.2 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.4 -> CurrentJDK lrwxr-xr-x 1 root wheel 5 May 24 09:07 1.3 -> 1.3.1 lrwxr-xr-x 1 root wheel 3 May 24 09:07 CurrentJDK -> 1.6Notice that there really isn’t a way to run a real 1.5 JRE on my machine since they are all linked to the CurrentJDK. Is your setup similar?
If not you could change your mappings to look like mine, in which case MyEclipse should launch with 1.6 the next time used. Or you can try setting the ini and info.plist files as you did before. The really issue you had there was that the workspace couldn’t find it’s JRE. If you set the JRE in your workspace to be 1.6 *before* you make these changes you should have less trouble. Personally, I like having all my links pointing to CurrentJDK and that pointing to 1.6.
Nikolaos,
This is interesting. Can you double-check the settings in /System/Library/Frameworks/JavaVM.framework/Versions
and see that they look like mine below?drwxr-xr-x 3 root wheel 102 Jul 20 2009 1.3.1 drwxr-xr-x 7 root wheel 238 Aug 14 2009 1.6.0 lrwxr-xr-x 1 root wheel 5 May 24 09:07 1.6 -> 1.6.0 lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.5.0 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.5 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.4.2 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.4 -> CurrentJDK lrwxr-xr-x 1 root wheel 5 May 24 09:07 1.3 -> 1.3.1 lrwxr-xr-x 1 root wheel 3 May 24 09:07 CurrentJDK -> 1.6Notice that there really isn’t a way to run a real 1.5 JRE on my machine since they are all linked to the CurrentJDK. Is your setup similar?
If not you could change your mappings to look like mine, in which case MyEclipse should launch with 1.6 the next time used. Or you can try setting the ini and info.plist files as you did before. The really issue you had there was that the workspace couldn’t find it’s JRE. If you set the JRE in your workspace to be 1.6 *before* you make these changes you should have less trouble. Personally, I like having all my links pointing to CurrentJDK and that pointing to 1.6.
Nikolaos,
This is interesting. Can you double-check the settings in /System/Library/Frameworks/JavaVM.framework/Versions
and see that they look like mine below?drwxr-xr-x 3 root wheel 102 Jul 20 2009 1.3.1 drwxr-xr-x 7 root wheel 238 Aug 14 2009 1.6.0 lrwxr-xr-x 1 root wheel 5 May 24 09:07 1.6 -> 1.6.0 lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.5.0 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.5 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.4.2 -> CurrentJDK lrwxr-xr-x 1 root wheel 10 May 24 09:07 1.4 -> CurrentJDK lrwxr-xr-x 1 root wheel 5 May 24 09:07 1.3 -> 1.3.1 lrwxr-xr-x 1 root wheel 3 May 24 09:07 CurrentJDK -> 1.6Notice that there really isn’t a way to run a real 1.5 JRE on my machine since they are all linked to the CurrentJDK. Is your setup similar?
If not you could change your mappings to look like mine, in which case MyEclipse should launch with 1.6 the next time used. Or you can try setting the ini and info.plist files as you did before. The really issue you had there was that the workspace couldn’t find it’s JRE. If you set the JRE in your workspace to be 1.6 *before* you make these changes you should have less trouble. Personally, I like having all my links pointing to CurrentJDK and that pointing to 1.6.
