Eclipse will not start after installing a plugin

channing.walton commented on 2009-01-12

I just retried this with a new install of galileo and a new workspace. I was able to restart eclipse when I hadn't installed any plugins, but after installing the scala plugin I got the same error.

thomas.watson commented on 2009-01-12

This seems to work on Windows. My guess is your config.ini got corrupted. Can you attach your config.ini file. In particular we need to know what the value of the property "osgi.framework" is and whether it points to the correct version of the org.eclipse.osgi file you have in the plugins directory.

pascal.rapicault commented on 2009-01-12

This is working fine for me as well on a vanilla I20090601 drop. Could you please provide a URL of the place where you got the eclipse drop you are running. Thx.

channing.walton commented on 2009-01-12

(In reply to comment #3)

This is working fine for me as well on a vanilla I20090601 drop. Could you please provide a URL of the place where you got the eclipse drop you are running. Thx.

http://download.eclipse.org/releases/galileo/ and downloaded http://www.eclipse.org/downloads/download.php?file=/releases/galileo/galileo-I20090110-0801-macosx-cocoa-x86.tar.gz

channing.walton commented on 2009-01-12

Attachment: config.ini config.ini after installing scala plugin

The scala plugin I installed is from this update site: http://www.scala-lang.org/scala-eclipse-plugin-nightly

channing.walton commented on 2009-01-12

Attachment: config.ini config.ini from drop

channing.walton commented on 2009-01-12

FYI: I've tried other update sites from clean installs of galileo-I20090110-0801-macosx-cocoa-x86 and all have the same result.

gladyston.agra.franca commented on 2009-01-13

Walton,

I have faced the same problem as you, the only way to force update working is accept the changes (without restart), and so shutdown/restart/change workspace the product.

channing.walton commented on 2009-01-13

(In reply to comment #8)

Walton,

I have faced the same problem as you, the only way to force update working is accept the changes (without restart), and so shutdown/restart/change workspace the product.

I tried what you suggested but the next time I quit eclipse I was unable to restart it.

richard.gronback commented on 2009-02-07

This happens for all of my p2-ified product builds in Amalgam (at least both Mac flavors, I've not tested the rest): http://www.eclipse.org/modeling/amalgam/downloads/

If I backup the original config.ini and restore it after installation, all is well.

Similar build scripts are generated for Galileo and Amalgam, so if there's something different I should be doing w.r.t. configuring p2 or using custom config.ini files, please let me know.

pascal.rapicault commented on 2009-02-09

I have been able to reproduce the problem. I think the pb comes from how the product is being built. From a quick glance at the metadata, this does not look quite like a complete product. It seems to me like if some files are being copied down rather than resulting from a proper p2 installation (e.g config.ini and eclipse.ini) and as such some key piece of information is missing.

For example I have noticed that there is no configuration unit setting the start level of simpleconfigurator, nor there is one for the reconciler bundle. Also I could not find anything setting the launcher name (setLauncherName action), nor did I see any IU for the launcher (but I may have missed it). This last point is probably what is the cause of all the problems since when we are looking for an eclipse.ini we do not find one and end up routing all path computation on bogus values.

richard.gronback commented on 2009-02-10

Thanks for taking a look, Pascal. You reminded me of the one thing in the build that's not plain vanilla PDE...

During the creation of the Mac product using the p2.director, a leftover Eclipse.app is present in addition to the galileo.app specified by the launcher setup in the galileo.product file:
-Xms40m -Xmx768m -XX:MaxPermSize=256m -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts
Long ago, I noticed that the .ini file within these was different and used to copy the one from Eclipse.app to the galileo.app before deleting the former. Specifically, these two lines were present in the "leftover" one:

-startup ../../../plugins/org.eclipse.equinox.launcher_1.0.200.v20090128-1500.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.0.0.v20081201-1815

It seems I need to restore my old workaround, as inserting these two lines in the galileo.ini solves this p2 installation issue on the Mac.

I can't seem to find it, but there must be a bug on this double .app folder problem when running a product build on the Mac.

Adding Andrew, as he may be able to point in the right direction.

channing.walton commented on 2009-02-17

This just happened again for me in 3.5M5. I don't really want to reinstall eclipse and plugins if I can avoid it. I Is there a workaround to get eclipse to start again after this happens?

richard.gronback commented on 2009-02-17

(In reply to comment #13)

This just happened again for me in 3.5M5. I don't really want to reinstall eclipse and plugins if I can avoid it. I Is there a workaround to get eclipse to start again after this happens?

See comment #10. Try replacing your config.ini with the original.

channing.walton commented on 2009-02-17

(In reply to comment #14)

See comment #10. Try replacing your config.ini with the original.

Thanks that worked.

channing.walton commented on 2009-04-13

In recent integration builds of 3.5, reverting the config.ini file doesn't work. I am now backing up my entire eclipse install so that I can revert if necessary. There is nothing in any logs I can see.

eric.hildum commented on 2009-07-27

This problem is also affecting the Eclipse Pulsar project. The current target milestone information appears to be invalid. Is anyone actually working on this bug?

cedric.brun commented on 2010-11-23

cleaning up Amalgam tickets, this one is no more relevant as the package is , since Helios, exclusively built through EPP which take cares of these stuff.

eclipse / amalgam

Eclipse will not start after installing a plugin #11