Issues with GWT Eclipse Plugin and Eclise Oxygen 1.a

[Oleg Cohen]

Greetings,

I am wondering if anybody else ran into an error like this:

java.lang.NoSuchMethodError: org.eclipse.jdt.internal.core.JavaProject.computePackageFragmentRoots(Lorg/eclipse/jdt/core/IClasspathEntry;Lorg/eclipse/jdt/internal/compiler/util/ObjectVector;Ljava/util/HashSet;Lorg/eclipse/jdt/core/IClasspathEntry;ZLjava/util/Map;)V

after upgrading to the most recent Eclipse Oxygen 1.a

I am having problems editing GWT properties of a project and also compiling my GWT application project as the GWT Project Validator fails with the above error.

Thanks!
Oleg

[Alexander Leshkin]

There is an related issue on github - https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/365. 

Also, https://github.com/gwt-plugins/gwt-eclipse-plugin/issues/364 contains some additional info.

[Sebastian]

Same here, Oxygen 1a asked to be installed and now the plugin stopped working.

I assume many people will have the problem since 1a is actively pushed to users now.

Does anybody have an idea how to best work around this?

Regards

Sebastian

[Rodolfo M. Raya]

Also experienced problems with Oxygen 1a. Had to go back to Oxygen 1 to keep the GWT plugin working.

FWIW, I don't have the Groovy plugin in my system.

Regards,

Rodolfo

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[Oleg Cohen]

I started with a clean Oxygen 1.a IDE and only installed the GWT plugin. It still fails.

Here is the full stacktrace of the exception:

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.validators.GWTProjectValidator.build(GWTProjectValidator.java:72)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

[Oleg Cohen]

According to the Stack Trace it seems the issue is actually not in the GWT plugin but in the Eclipse Google plugin

com.google.gdt.eclipse.core.

ClasspathUtilities.findRawClasspathEntryFor(ClasspathUtilities.java:163)

So, not sure how that one is maintained and updated.

[Jens]

It isn't. It is deprecated and scheduled for deletion in January 2018. You should use Cloud Tools for Eclipse if you need AppEngine.

-- J.

[Jens]

It isn't. It is deprecated and scheduled for deletion in January 2018. You should use Cloud Tools for Eclipse if you need AppEngine.

See red notice below the header menu: https://developers.google.com/eclipse/ 

-- J.

[Oleg Cohen]

Thank you for the info. I saw that too.

Here is also what is on that page:

* For GWT, install the GWT Eclipse plugin.

The GWT Eclipse plugin is the one that is having issues. Does the Cloud Tools for Eclipse include GWT?

[Oleg Cohen]

This discussion might be helpful: https://bugs.eclipse.org/bugs/show_bug.cgi?id=525462

Xtext is having similar issues. Apparently it is due to the use of internal JDT API that got broken in Oxygen 1.a. It should be back with Oxygen 2 to provide backward compatibility to existing packages that are broken due to the API change.

[Jens]

The GWT Eclipse plugin is the one that is having issues. Does the Cloud Tools for Eclipse include GWT?

No. The Google Eclipse Plugin (deprecated) has been split up into two separate plugins. The Cloud Tools Plugin does not contain any GWT stuff.

-- J. 

[Sebastian]

I too use the new GWT Plugin, not the deprecated Google one. 

I had to downgrade Eclipse to be able to work and don't remember the exact complete stack trace, but the top was certainly something like

[Brandon Donnelson]

I'm working on the issue for the GWT Eclipse Plugin. It's fixed in a later version. The Eclipse API has had a regression. 

[Brandon Donnelson]

The fix is getting pushed up to the GWT Eclipse Plugin snapshot and release now. 

[blink]

Thank you very much!