https://bugzilla.redhat.com/show_bug.cgi?id=1392150
--- Comment #7 from Roland Grunberg <rgrunber(a)redhat.com> ---
I'm able to reproduce this by starting on a fresh Eclipse workspace, and
attempting to debug some java project and selecting "Yes" for the prompt that
asks whether to open the Debug perspective for that session when a breakpoint
is hit.
Looking in the error logs, I see stacktraces similar to :
!ENTRY org.eclipse.e4.ui.workbench 4 0 2016-11-09 14:00:56.893
!MESSAGE Unable to load resource
file:/tmp/foo/workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
!STACK 0
java.lang.NullPointerException
at
org.eclipse.e4.ui.internal.workbench.ResourceHandler.getResource(ResourceHandler.java:289)
at
org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadResource(ResourceHandler.java:265)
at
org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:169)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:377)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:252)
...
...
This happens at :
http://git.eclipse.org/c/platform/eclipse.platform.ui.git/tree/bundles/or...
The failures to load the workbench.xmi seem to be happening because the
@PostConstruct init() in ResourceHandler (
http://git.eclipse.org/c/platform/eclipse.platform.ui.git/tree/bundles/or...
) is never triggered, so resourceSetImpl remains null in Fedora Eclipse. This
is what ultimately leads to the NPE in getResource(URI uri). On an Upstream
Eclipse it is triggered and this issue doesn't seem to occur.
If I look at the wiring for the 'javax.annoation' package I see :
g! packages javax.annotation
osgi.wiring.package; bundle-symbolic-name="javax.annotation-api";
bundle-version:Version="1.2.0"; version:Version="1.2.0";
osgi.wiring.package="javax.annotation"<javax.annotation-api_1.2.0 [7]>
org.eclipse.e4.ui.workbench.addons.swt_1.2.100.v20160915-0852 [74] imports
org.eclipse.e4.ui.workbench_1.4.0.v20160915-0852 [73] imports
org.eclipse.e4.tools.emf.ui_4.5.100.v20160915-0852 [993] imports
org.eclipse.e4.tools.services_4.5.0.v20160915-0852 [995] imports
com.google.guava_18.0.0 [869] imports
org.eclipse.e4.ui.workbench.renderers.swt_0.14.0.v20160915-0852 [75] imports
org.eclipse.launchbar.ui.controls_1.0.0.201610040941 [1090] imports
org.eclipse.e4.ui.workbench.swt_0.14.1.v20160915-0852 [76] imports
org.eclipse.ui.workbench_3.108.1.v20160915-0852 [188] imports
org.eclipse.e4.ui.css.swt.theme_0.10.100.v20160915-0852 [66] imports
osgi.wiring.package;
bundle-symbolic-name:List<String>="org.eclipse.osgi,system.bundle";
bundle-version:Version="3.11.1.v20160915-0852";
version:Version="0.0.0";
osgi.wiring.package="javax.annotation"<org.eclipse.osgi_3.11.1.v20160915-0852
[0]>
org.eclipse.e4.core.services_2.0.100.v20160915-0852 [61] imports
org.eclipse.rse.services.dstore_3.3.0.201610041547 [1297] imports
org.eclipse.cdt.debug.core_8.0.0.201609122005 [942] imports
org.eclipse.emf.codegen.ui_2.6.0.v20160613-1000 [1012] imports
...
...
everything else
...
...
It looks like the e4.ui.workbench plugins are being wired against the wrong
javax.annotation. On the first startup they were fine but after performing the
steps to reproduce, they seem to be wired differently.
--
You are receiving this mail because:
You are on the CC list for the bug.