Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Eclipse Oxygen.1 Plugin Error due wrong interface

See original GitHub issue

Eclipse has change an interface.

I have updated from old GWT Plugin to new one but error still occurs

They have added a additional boolean: https://github.com/eclipse/eclipse.jdt.core/blob/master/org.eclipse.jdt.core/model/org/eclipse/jdt/internal/core/JavaProject.java

Change comes with: https://github.com/eclipse/eclipse.jdt.core/commit/54049bd43ee6ccfbd3f1b67192d2ed3baee764e3#diff-c1da82ed737689b0aeddf1126c08e061


java.lang.NoSuchMethodError: org.eclipse.jdt.internal.core.JavaProject.computePackageFragmentRoots([Lorg/eclipse/jdt/core/IClasspathEntry;ZLjava/util/Map;)[Lorg/eclipse/jdt/core/IPackageFragmentRoot;
	at com.google.gdt.eclipse.core.ClasspathUtilities.findRawClasspathEntryFor(ClasspathUtilities.java:163)
	at com.google.gwt.eclipse.core.runtime.GwtSdk$ProjectBoundSdk.findGwtDevClasspathEntry(GwtSdk.java:361)
	at com.google.gwt.eclipse.core.runtime.GwtSdk$ProjectBoundSdk.computeInstallPath(GwtSdk.java:266)
	at com.google.gwt.eclipse.core.runtime.GwtSdk$ProjectBoundSdk.getInstallationPath(GwtSdk.java:189)
	at com.google.gwt.eclipse.core.runtime.GwtSdk.findSdkFor(GwtSdk.java:411)
	at com.google.gwt.eclipse.core.launch.processors.DGwtDevJarArgumentProcessor.maybeGetDevJarPath(DGwtDevJarArgumentProcessor.java:76)
	at com.google.gwt.eclipse.core.launch.processors.DGwtDevJarArgumentProcessor.update(DGwtDevJarArgumentProcessor.java:123)
	at com.google.gdt.eclipse.suite.launch.processors.LaunchConfigurationUpdater.update(LaunchConfigurationUpdater.java:141)
	at com.google.gdt.eclipse.suite.launch.processors.LaunchConfigAffectingChangesListener.syncUpdate(LaunchConfigAffectingChangesListener.java:93)
	at com.google.gdt.eclipse.suite.launch.processors.LaunchConfigAffectingChangesListener.access$2(LaunchConfigAffectingChangesListener.java:89)
	at com.google.gdt.eclipse.suite.launch.processors.LaunchConfigAffectingChangesListener$1.runInWorkspace(LaunchConfigAffectingChangesListener.java:78)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)```

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:32 (17 by maintainers)

Top GitHub Comments

2reactions

branflake2267commented, Oct 13, 2017

Fix getting pushed to staging.

1reaction

zecrittercommented, Feb 13, 2018

I can confirm, clean Oxygen 4.7.2 with initially empty workspace/configuration + gwt 2.8.2 + stable GWT Eclipse Plugin 3.0.0.201710131939 + imported gwt projects work without problems.