- This topic has 2 replies, 2 voices, and was last updated 16 years, 6 months ago by Lance Drake.
-
AuthorPosts
-
Lance DrakeMemberHi MyEclipse Support,
Despite trying every possible combination of ECLIPSE & MYECLIPSE – reading thru the Eclipse.org archives – checking the MyEclipse archives – doing a Google search – and otherwise making every effort to answer my own question prior to posting here, I must report I am at a loss for what is happening and why I cannot launch the Eclipse/MyEclipse IDE application in my Mac tower running Leopard v10.5.3 build 9D29
BTW: I mention the version of Leopard only to be specific – I have had the same problem with earlier versions of Leopard but imagined I simply needed to be more deliberate and also let a little time go by for the Eclipse developers to attend to whatever was the problem. So – this is not something new with 10.5.3, per se.
BELOW: The complaint which ends up as a file in the eclipse/configuration folder says it’s something basic and something serious.
!SESSION 2008-05-12 00:49:48.727 ----------------------------------------------- eclipse.buildId=M20071023-1652 java.version=1.5.0_13 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US Framework arguments: -keyring /Users/lance/.eclipse_keyring -showlocation -product com.genuitec.myeclipse.product.ide Command-line arguments: -os macosx -ws carbon -arch x86 -keyring /Users/lance/.eclipse_keyring -consoleLog -showlocation -product com.genuitec.myeclipse.product.ide !ENTRY org.eclipse.update.configurator 4 0 2008-05-12 00:49:49.545 !MESSAGE !STACK 0 org.osgi.framework.BundleException: Exception in org.eclipse.update.internal.configurator.ConfigurationActivator.start() of bundle org.eclipse.update.configurator. at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1018) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297) Caused by: org.eclipse.core.runtime.CoreException: Cannot create configuration in file:/DEVELOPER/eclipse/configuration/ at org.eclipse.update.internal.configurator.Utils.newCoreException(Utils.java:96) at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize(ConfigurationActivator.java:113) at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:69) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999) at java.security.AccessController.doPrivileged(Native Method) ...and so on...
Does anyone have a clue or work-around for this? I was under the impression that Eclipse/MyEclipse worked with MacOSX 10.5 [LEOPARD] – is this not the case?
Thanks very much for your response to my question.
Best Wishes,
Lance Drake
Loyal WaterMemberLance,
What happens when you try to run Eclipse without installing MyEclipse on it ? Do you still get the same set of errors ?Have you tried using pulse (www.poweredbypulse.com) to launch MyEclipse?
Lance DrakeMemberHi MyEclipse Support,
Exactly as you suggested, I finally got to the point where I decided to see if Eclipse would run on its own – without installing MyEclipse. Of course, the answer was “No…”.
So I created a new TIGER 10.4 boot drive – installed Eclipse – it ran – installed MyEclipse – it ran – pointed at my project workspace and realized… DUDE!… you need to copy the extra java jar files needed to compile into your /Library/Java/Extensions folder.
Miraculously, at that point everything stopped working. Of course I started scratching my head as this very batch of jar files WAS working with TIGER before I attempted to upgrade to LEOPARD.
So, I pulled all of the jars out of that folder – low and behold MyEclipse launched with no problem. A list of the files which I did not re-include is below. I stopped adding things back when my project compiled and I could run XDoclet with no errors. I suppose it’d be REALLY cool if I discovered which of the below was the real culprit.
gnujaxp.jar itext-2.0.6.jar saxon8.jar xalan.jar xercesImpl.jar xml-apis.jar
OK – life is good again – and, yes, Eclipse/MyEclipse DOES run on Leopard.
Best Regads,
Lance Drake
-
AuthorPosts