Re: Problem compiling GWT code with Java9
FYI. Google released a GWT update in October (http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_2) that supposed includes fixes to allow it to work with Java9. We'll be trying that soon. On Thursday, September 21, 2017 at 12:21:19 AM UTC-7, Thomas Broyer wrote: > > Fwiw, I confirm that HEAD-SNAPSHOT works with Java 9: > https://travis-ci.org/tbroyer/gwt-maven-plugin/jobs/277854932 > > On Wednesday, September 20, 2017 at 10:06:51 AM UTC+2, Thomas Broyer wrote: >> >> There have been some changes [1,2] to make it (at least partially) work >> with a Java 9 VM; you can try HEAD-SNAPSHOT (from >> https://oss.sonatype.org/content/repositories/google-snapshots/) until >> we release 2.8.2 with the changes. >> >> [1] >> https://github.com/gwtproject/gwt/commit/87f27659af55d7d549521405ef10889e8dfe3f3a >> [2] >> https://github.com/gwtproject/gwt/commit/5b7560c4bb6376e997981387e4f2feee1816e1dc >> >> On Wednesday, September 20, 2017 at 9:49:20 AM UTC+2, Pratik Parikh wrote: >>> >>> does anyone have an update on this sissu? I am running into the same >>> problem, so an update would help. >>> >>> On Tuesday, June 13, 2017 at 12:08:29 PM UTC-4, James Nelson wrote: Hi. I am currently very busy this week, but can try to schedule a push to maven central this weekend (I have other people waiting on it to use various other tools I dabble in as well). Please remind me if I don't post links back here by next Monday. Worst case scenario, I can just upload jars to github and push a gist of the pom I used, with some instructions on how to set the system properties to make it work. I used the IDE to handle vm args, as standard maven plugins are less amenable to hacking / debugging (though I'm sure it must be possible, I did not have enough free time to get that far on it). I'll probably update to latest java 9 spec, since the module system has undergone another iteration since I tried these hacks. Please keep in mind, however, that my fork has diverged from mainline for quite a while, and does not undergo the same rigorous testing that you might expect. In particular, if you start using any of the other features I've added (reflection, arbitrary magic method injection), it can break incremental recompilations. It's a known issue I'm avoiding looking at, since most of the 2.X stack is going to go away, and I have to migrate all my magic into apt-generators to run as a pre-gwtc stage. While I might be able to help you get something that works as a proof of concept, I would urge you to hold off on using it in production, as I am not (yet) ready to offer fulltime support. A couple colleagues and I are playing with the idea of offering fulltime support and maintenance of 2.X around mid-September (barring a funding miracle for our current money-source). So, please take this caveats to heart; I can probably get you up and compiling, but this should all be viewed as experimental and not-production ready for a while yet. >>> -- 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-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Problem compiling GWT code with Java9
At Labkey.com we're trying to compile all of our code, which includes GWT code, with Java9 (due for release in the summer)getting a head start. We have not been able to compile GWT code, which doesn't use any new Java features. We're getting the error [java] Compiling module org.labkey.experiment.property.Designer [java][ERROR] Unable to find type 'java.lang.Object' [java] [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') We've had an older version of GWT but have tried with the latest 2.8 as well and get the same thing. I've added -logLevel=DEBUG to get more info and the log says we're inheriting all of the appropriate packages, including com.google.gwt.core.Core and com.google.gwt.emul.Emulation, which of course is where java.lang.Object lives. It seems like something is going wrong with gwt-unitCache because the log looks like this: ..lots of inherits before this.. [java] Module location: file:/Users/davebradlee/trunk/server/internal/gwtsrc/org/labkey/api/gwt/Internal.gwt.xml [java] Loading inherited module 'com.extjs.gxt.ui.GXT' [java] Module location: jar:file:/Users/davebradlee/trunk/external/lib/build/gxt.jar!/com/extjs/gxt/ui/GXT.gwt.xml [java] Loading inherited module 'com.google.gwt.json.JSON' [java] Module location: jar:file:/Users/davebradlee/trunk/external/lib/build/gwt-user.jar!/com/google/gwt/json/JSON.gwt.xml [java] Loading inherited module 'com.allen_sauer.gwt.dnd.gwt-dnd' [java] Module location: jar:file:/Users/davebradlee/trunk/external/lib/server/gwt-dnd-3.2.0.jar!/com/allen_sauer/gwt/dnd/gwt-dnd.gwt.xml [java] Public resources found in... [java] Translatable source found in... [java] Persistent unit cache dir set to: /Users/davebradlee/trunk/build/modules/experiment/explodedModule/gwt-unitCache [java] Opening cache file: /Users/davebradlee/trunk/build/modules/experiment/explodedModule/gwt-unitCache/gwt-unitCache-6a094daf5d20bb65adf2d207cc48308bde849f64-015A3E41072B [java] Looking for previously cached Compilation Units in /Users/davebradlee/trunk/build/modules/experiment/explodedModule/gwt-unitCache [java] Compiling module org.labkey.experiment.property.Designer [java]Found 0 cached/archived units. Used 0 / 0 units from cache. [java]Compiling... [java] Compilation completed in 0.00 seconds [java]PersistentUnitCache cleanup requested [java]Added 0 units to PersistentUnitCache since last cleanup [java]Skipped PersistentUnitCache because no units were added [java]Removing invalidated units [java]Resolving enclosing classes [java]Tracing compile failure path for type 'java.lang.Object' [java] Checked 0 dependencies for errors. [java][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') [java] Closing cache file: /Users/davebradlee/trunk/build/modules/experiment/explodedModule/gwt-unitCache/gwt-unitCache-6a094daf5d20bb65adf2d207cc48308bde849f64-015A3E41072B (0 units written) [java] Deleting empty file: /Users/davebradlee/trunk/build/modules/experiment/explodedModule/gwt-unitCache/gwt-unitCache-6a094daf5d20bb65adf2d207cc48308bde849f64-015A3E41072B [java] Shutting down PersistentUnitCache thread Using Java8 the log looks like this ... [java] Persistent unit cache dir set to: /Users/davebradlee/trunk/build/modules/experiment/explodedModule/gwt-unitCache [java] Opening cache file: /Users/davebradlee/trunk/build/modules/experiment/explodedModule/gwt-unitCache/gwt-unitCache-6a094daf5d20bb65adf2d207cc48308bde849f64-015A3E53CB49 [java] Looking for previously cached Compilation Units in /Users/davebradlee/trunk/build/modules/experiment/explodedModule/gwt-unitCache [java] Compiling module org.labkey.experiment.property.Designer [java]Found 0 cached/archived units. Used 0 / 3794 units from cache. [java]Compiling... [java] 60% complete (ETR: 3 seconds) [java] 60% complete (ETR: 3 seconds) [java] 60% complete (ETR: 3 seconds) [java] 60% complete (ETR: 3 seconds) [java] 60% complete (ETR: 3 seconds) [java] 60% complete (ETR: 3 seconds) [java] 60% complete (ETR: 3 seconds) [java] 70% complete (ETR: 2 seconds) [java] 80% complete (ETR: 2 seconds) [java] 90% complete (ETR: 1 seconds) [java] 100% complete (ETR: 0 seconds) [java] Compilation completed in 10.80 seconds [java]PersistentUnitCache cleanup requested [java]Added 3794 units to PersistentUnitCache since last cleanup
