The error suggests a class path issue. The same patch that introduced <window> in native string relaxed the checking for namespaces in the compiler to allow this situation ( https://gwt-review.googlesource.com/#/c/16881/).
On Wed, Sep 21, 2016 at 2:46 AM, stuckagain <[email protected]> wrote: > It looks like some changes to JSInterop are breaking my build.... > > Compiling module com.swift.common.paging.PagingTest.JUnit > Ignored 1 unit with compilation errors in first pass. > Compile with -strict or with -logLevel set to TRACE or DEBUG to see all > errors. > Errors in com/google/gwt/emul/java/lang/String.java > [ERROR] Line 165: 'String.NativeFunction > String.getFromCharCodeFunction()' > has invalid namespace '<window>'. > [ERROR] Line 757: 'String.NativeString' has invalid namespace > '<window>'. > > Additionally, how can I enable strict mode for GWTTestCases when using > tbroyer's maven plugin ? > > -- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/google-web-toolkit-contributors/5e035a47-ff94- > 4bfa-869e-fee8fb1dd0fc%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmZYsv%3DEknBAVUvsS_Dv_TKYex9dHD39G%2B3-tKT6Qf0wg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
