SNAPSHOT of 21 Sept breaks my build (invalid namespace <window>

[stuckagain]

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 ?

[Thomas Broyer]

On Wednesday, September 21, 2016 at 11:46:25 AM UTC+2, stuckagain 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>'.

Make (extra)sure you have the latest gwt-dev as well.

 

Additionally, how can I enable strict mode for GWTTestCases when using tbroyer's maven plugin ?

This actually is not possible, and a limitation of GWT itself (JUnitShell doesn't support -strict or -failOnError). 

[David]

I'm using maven and I only have a dependency on 2.8.0-SNAPSHOT.
I have forced an update of the snapshots in an eclipse refresh and now it seems to work.
I guess it was a local maven/nexus issue ?

I hope -strict becomes the default, why would you want to ignore errors ? In most cases it is hiding some issue that will surface later.

--
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 google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/e3ffcc03-8b4b-4cc1-b9eb-936d0232dde3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Roberto Lublinerman]

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/).

--
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 google-web-toolkit-contributors+unsubscribe@googlegroups.com.
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.