The error suggests a class path issue. The same patch that introduced
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 wrote:
> It
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
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
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