Re: [equinox-dev] Fwd: Starting a runtime Eclipse fails with Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator.

2016-06-30 Thread Lars Vogel
Thanks Thomas for the fast fix. > I would not know how to get p2 to install a bundle with no symbolic name. IIRC I used a fresh 4.7 download without any additional plug-ins, imported all projects in the eclipse.pde.ui repo and started Eclipse from. I test this tomorrow with a fresh I-Build.

Re: [equinox-dev] Fwd: Starting a runtime Eclipse fails with Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator.

2016-06-30 Thread Thomas Watson
FYI, I decided to open this bug myself so I could get a fix going while it was fresh in my mind: https://bugs.eclipse.org/bugs/show_bug.cgi?id=497094 Although I don't have any way to test this since I would not know how to get p2 to install a bundle with no symbolic name. Tom From:

Re: [equinox-dev] Fwd: Starting a runtime Eclipse fails with Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator.

2016-06-30 Thread Thomas Watson
Some bundle in your environment looks like it has no Bundle-SymbolicName. Can you open a bug against p2. It needs a null check at ConfigApplier.refreshPackages(ConfigApplier.java:401) But I am curious how you got p2 to install a bundle with no Bundle-SymbolicName. I thought that was

[equinox-dev] Fwd: Starting a runtime Eclipse fails with Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator.

2016-06-29 Thread Lars Vogel
Hi Friends of Equinox, if I start an runtime Eclipse from the pde.ui repository I get the error that org.eclipse.equinox.simpleconfigurator_1.1.200.v20160504-1450 [2439] is not active. Stack trace below. Do you have suggestions how to solve this issue? My "normal" strategies for a Eclipse