Wednesday, October 11, 2017

Re: Contributing: eclipse README outdated?

As always, you spotted it right! (except for the blacklist: only **/ is necessary)

I will submit a patch for .eclipse/user/.classpath.

But just to know, Google doesn't use Eclipse internally? 
I'm an IntelliJ user, it would be great to have a REAME for IntelliJ.

Anyway Thanks so much!

On Tuesday, October 10, 2017 at 9:39:03 PM UTC+11, Thomas Broyer wrote:
It's highly probable that the provided Eclipse configuration (in this case eclipse/user/.classpath) is outdated.
It looks like you'd have to add "core/super/com/google/gwt/emul" ("core" being "user" actually on disk) as a source root but only whitelist javaemul/internal/**/*.java , and blacklist **/, **/, **/, **/ and **/ (according to user/build.xml line 101)

On Tuesday, October 10, 2017 at 7:50:26 AM UTC+2, Freddy Boucher wrote:

I followed the eclipse README to setup a working environment to contribute but it fails with the following errors:
  • ArrayHelper cannot be resolved
  • ArrayHelper cannot be resolved to a variable
  • Coercions cannot be resolved
  • ConsoleLogger cannot be resolved
  • DoNotInline cannot be resolved to a type
  • HasNoSideEffects cannot be resolved to a type
  • The import javaemul cannot be resolved
  • The import javaemul.internal cannot be resolved
  • UncheckedCast cannot be resolved to a type
I tried with a clean Eclipse Oxygen.1 Release (4.7.1)

Is the README outdated? Did I miss a step?


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
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment