[vijayagorla]

Hi,

I have problem running myEclipse with my existing workspace. But when I tried reinstalling myeclipse and opened with new workspace it worked. Could you please suggest me how to make it work with the existing work space.. I am gueesing if this is related to heap size or any thing..

It gives the following pop-up
JVM Terminated Exit code 1

Thanks
Vijaya.

[Riyad Kalla]

Vijaya,

Try and edit the shortcut used to start MyEclipse, and add the “-clean” command line argument as the first argument in the command line (Before -vm or -vmargs) then fire it up and try and open your existing workspace. Did that work?

[vijayagorla]

I tried it.. still have the same problem.

[Riyad Kalla]

Vijaya,

If MyEclipse cannot even open the workspace using -clean it looks like the workspace got corrupted somehow… try and create a new workspace and use File > Import > Existing Project, and select the “Root Dir” of your old workspace, and check “Copy into new workspace” that should copy across all your projects into the new workspace for you… I’m sorry, I’m not sure what went wrong.

Out of curiosity is any exception being logged to <corrupt workspace dir>\.metadata\.log at the end of the file when it fails to load?

[Jay Kirby]

I’m having a similar problem with a new install of 6.5. I made a copy of my 5.5.1 workspace and successfully opened it a few times, but now see the following in the .log:

!SESSION 2008-08-20 13:36:28.565 ———————————————–
eclipse.buildId=M20080221-1800
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -clean -clean

!ENTRY org.eclipse.update.configurator 2008-08-20 13:37:23.962
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/com.ibm.icu_3.6.1.v20070906.jar Bundle “com.ibm.icu” version “3.6.1.v20070906” has already been installed from: update@plugins/com.ibm.icu_3.6.1.v20070906.jar

!ENTRY org.eclipse.update.configurator 2008-08-20 13:37:24.478
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/javax.servlet.jsp_2.0.0.v200706191603.jar Bundle “javax.servlet.jsp” version “2.0.0.v200706191603” has already been installed from: update@plugins/javax.servlet.jsp_2.0.0.v200706191603.jar

!ENTRY org.eclipse.update.configurator 2008-08-20 13:37:24.509
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/javax.servlet_2.4.0.v200706111738.jar Bundle “javax.servlet” version “2.4.0.v200706111738” has already been installed from: update@plugins/javax.servlet_2.4.0.v200706111738.jar

!ENTRY org.eclipse.update.configurator 2008-08-20 13:37:25.307
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/org.apache.commons.el_1.0.0.v200706111724.jar Bundle “org.apache.commons.el” version “1.0.0.v200706111724” has already been installed from: update@plugins/org.apache.commons.el_1.0.0.v200706111724.jar

!ENTRY org.eclipse.update.configurator 2008-08-20 13:37:35.939
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/org.mozilla.xpcom_1.8.1.3-20070320/ Bundle “org.mozilla.xpcom” version “1.8.1.3-20070320” has already been installed from: update@../../../eclipse/plugins/org.mozilla.xpcom_1.8.1.3-20070320/

!ENTRY org.eclipse.update.configurator 2008-08-20 13:37:35.986
!MESSAGE Could not install bundle ../myeclipse/eclipse/plugins/org.mozilla.xulrunner.win32.win32.x86_1.8.1.3-20070404/ Bundle “org.mozilla.xulrunner.win32.win32.x86” version “1.8.1.3-20070404” has already been installed from: update@../../../eclipse/plugins/org.mozilla.xulrunner.win32.win32.x86_1.8.1.3-20070404/

!ENTRY org.eclipse.ui 2 0 2008-08-20 13:38:05.130
!MESSAGE Warnings while parsing the key bindings from the ‘org.eclipse.ui.commands’ extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2008-08-20 13:38:05.130
!MESSAGE Cannot bind to an undefined command: plug-in=’com.aptana.ide.editors’, id=’org.eclipse.ui.edit.text.openExternalFile’

!ENTRY org.eclipse.ui.workbench 4 0 2008-08-20 13:38:34.259
!MESSAGE Widget disposed too early!
!STACK 0
java.lang.RuntimeException: Widget disposed too early!
at org.eclipse.ui.internal.WorkbenchPartReference$1.widgetDisposed(WorkbenchPartReference.java:169)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:116)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943)
at org.eclipse.swt.widgets.Widget.release(Widget.java:740)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:662)
at org.eclipse.swt.widgets.Widget.release(Widget.java:743)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:662)
at org.eclipse.swt.widgets.Widget.release(Widget.java:743)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:662)
at org.eclipse.swt.widgets.Widget.release(Widget.java:743)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:662)
at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:117)
at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:766)
at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1134)
at org.eclipse.swt.widgets.Widget.release(Widget.java:743)
at org.eclipse.swt.widgets.Widget.dispose(Widget.java:410)
at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:441)
at org.eclipse.swt.widgets.Shell.dispose(Shell.java:653)
at org.eclipse.swt.widgets.Display.release(Display.java:3341)
at org.eclipse.swt.graphics.Device.dispose(Device.java:261)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:122)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)

[Riyad Kalla]

Malone,

What happened when you tried to restart after adding -clean in the shortcut used to start MyEclipse?

[Jay Kirby]

Clean made no difference, so I ended up recopying my old 5.5.1 workspace again. I’ve learned not to use the same workspace during version upgrades, since it’s pretty common that something gets fouled up (I have a few other plugins) and it gives me a base workspace version I can start over with. I just make a copy and use that with the new version.

To make the workspace smaller, my projects are always in a different location than the workspace – still seems like there’s a lot of stuff in the workspace though (2 GB), probably because the logs and caches are buried in there somewhere. It would be nice if there was some way to migrate my workspace preferences to a new workspace without making a copy of everything in the source one.

Now I’m just getting a NPE when it automatically searches for updates, which I can live with:

!ENTRY org.eclipse.core.jobs 4 2 2008-08-21 09:13:45.630
!MESSAGE An internal error occurred during: “Searching for updates”.
!STACK 0
java.lang.NullPointerException
at org.eclipse.update.search.UpdateSearchRequest.performSearch(UpdateSearchRequest.java:287)
at org.eclipse.update.ui.UpdateJob.runUpdates(UpdateJob.java:207)
at org.eclipse.update.ui.UpdateJob.run(UpdateJob.java:168)
at com.aptana.ide.core.ui.update.AutomaticUpdateJob.run(AutomaticUpdateJob.java:70)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

One other weird thing with the new workspace is I now also get an error the first time I run an ant task. If I rerun it then works fine:

Errors during build.
Errors running builder ‘Integrated External Tool Builder’ on project ‘myproject’.
Variable references empty selection: ${project_path}

[Riyad Kalla]

To make the workspace smaller, my projects are always in a different location than the workspace – still seems like there’s a lot of stuff in the workspace though (2 GB), probably because the logs and caches are buried in there somewhere. It would be nice if there was some way to migrate my workspace preferences to a new workspace without making a copy of everything in the source one.

Oh there is, fire up your old workspace, use File > Export > Preferences, and export the prefs. Then use File > Import > Preferences from the new workspace to pull them in, and File > Import> Existing Projects to pull those projects after from the old workspace to the new one.

Actually, try this instead of copying the workspace, see if the spurious errors disappear.

[Jay Kirby]

That’s fine for basic settings, but I change the layout of my perspectives and that isn’t remembered with the preferences import/export (unfortunately). Also, it didn’t remember settings for some plugins (like one of the source control systems we use, perforce)….
And it didn’t help with the build error I was seeing the the Integrated External Builder.

Another problem with the export/import approach is that myeclipse libraries (like spring) still point to the old version location (my 6.5 now points to 5.5.1 libraries).

[Riyad Kalla]

Another problem with the export/import approach is that myeclipse libraries (like spring) still point to the old version location (my 6.5 now points to 5.5.1 libraries).

You can fix this by going to the Window > Prefs > MyEclipse > Project Capabilities preferences and using the “Restore Defaults” button to reset those when they get out of whack.

[Author]

Posts