So I think Thomas is right. One of our change in this new release was to rename toString() method on some objects to avoid confusion with java.lang.Object methods. That broke Elemental with J2CL because java.lang.Object is a JsType in J2CL and we need to lift up some jsinterop restriction to allows user to override an implementation with a native override (something similar to https://gwt-review.googlesource.com/c/gwt/+/20122) But in GWT, Object is not a JsType and we don't have that problem. So we dont need https://gwt-review.googlesource.com/c/gwt/+/20122 for Elemental in GWT.
The good news is Elemental2:1.0.0-beta-3 is working with the current version of GWT. Sorry for the confusion. On Mon, Dec 4, 2017 at 11:08 PM Thomas Broyer <t.bro...@gmail.com> wrote: > There must be some cases where it requires the current head, but so far I > haven't had any issue with 2.8.2. > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/bb66fed8-82a5-4b80-a36c-c223578d7e8c%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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D7cdZwbC5uVHkBTQ%3DAr8vZ%2BgqMzDWoQ6_gS0AO43tU6ww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
