[GWT] [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core'

Skip to first unread message

Clint Yang

May 19, 2019, 7:49:52 AM5/19/19
to GWT Users
Hi all,

I haven't done GWT development for a while and wanted to try again. I installed JDK 12 and Eclipse 2019-03. I installed GWT Eclipse Plugin (GWT 2.8.1). 

From Eclipse, I created a hello world project this way:
  1. Click on 'New GWT Application Project'
  2.  Project name: Gwt5, Package: com.foo, Use default SDK (GWT 2.8.1)
  3. Click on 'GWT Compile Project'
I see this error:

Compiling module com.foo.Gwt5
   [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core' either directly or indirectly (most often by inheriting module 'com.google.gwt.user.User')

I didn't change my gwt.xml.

Any suggestion?

Craig Mitchell

May 19, 2019, 8:59:25 PM5/19/19
to GWT Users
I don't believe GWT supports Java 12 yet.  I'd recommend just using Java 8.

And you might want to use the latest GWT version (2.8.2).

Christian Nzhie

Oct 7, 2022, 8:51:17 AM10/7/22
to GWT Users
Hello here.
I would like to react for this threat. Would at this time (2022) gwt supports java 12?
For I am experiencing the error mentioned above.
Thanks in advance.

Michael Conrad

Oct 7, 2022, 9:10:19 AM10/7/22
to google-we...@googlegroups.com
We are using JDK 17 here at the office for builds without any issue. (Gradle setup here).
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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/9e0c2d5e-770b-4884-887a-3e300a2ac28an%40googlegroups.com.

Thomas Broyer

Oct 7, 2022, 9:14:31 AM10/7/22
to GWT Users
See https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
GWT *runs* on JDKs from 8 to 17; you can however only compile Java 11 –at most– source files (depending on -sourceLevel).

When facing that kind of error, make sure you run with -failOnError (or its older name: -strict), and possibly use a more verbose -logLevel.
Reply all
Reply to author
0 new messages