Eclipse 3.x to E4 uplift. Could not start styling support…A null service reference is not allowed

Question

We have an RCP application that is running on the Eclipse 3.x platform and we're working on migrating it to pure E4 in the future. But just for now we're trying to pull in all the necessary dependencies. The app complies and runs but we get this stack trace at startup.

!ENTRY org.eclipse.ui 2 2 2016-03-15 14:34:36.241 !MESSAGE Could not start styling support. !STACK 0 java.lang.NullPointerException: A null service reference is not allowed. at org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:617) at org.eclipse.e4.ui.css.swt.internal.theme.BootstrapTheme3x.<init>(BootstrapTheme3x.java:38) at org.eclipse.e4.ui.css.swt.internal.theme.BootstrapTheme3x.<init>(BootstrapTheme3x.java:30) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2532) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) at org.eclipse.equinox.launcher.Main.run(Main.java:1515) at org.eclipse.equinox.launcher.Main.main(Main.java:1488)

There is one link out in the wild with a similar problem, but it's pretty out dated at this point.

Any help would be very appreciated!

Update I've tried out link which seems to be a similar issue. But that didn't fix it. I'm also wondering at this point if I have to many dependencies, and one is causing a conflict.

Answer 1

Okay after research I came across another post with a similar issue. I implemented this and it solved my problem.