[gwt-contrib] Re: Elemental2:1.0.0-beta-3 released

Why and what for "latest HEAD_SNAPSHOT release of GWT " is requered? I don't see any "serious"

[gwt-contrib] Re: Elemental2:1.0.0-beta-3 released

Correction of my previous email: Elemental2:1.0.0-beta-3 is working with the current version of GWT. You don't need to use the HEAD_SNAPSHOT release of GWT. Sorry for the confusion. -Julien On Tue, Dec 5, 2017 at 9:54 AM Julien Dramaix wrote: > I've released a Elemental2:1.0.0-beta-3 yesterday

Re: [gwt-contrib] Re: Elemental2:1.0.0-beta-2 released

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

[gwt-contrib] Elemental2:1.0.0-beta-3 released

I've released a Elemental2:1.0.0-beta-3 yesterday in order to fix the maven issue. As usual, elemental2 is split into small jar files: Jar file artifact-id GWT module elemental2-core.jar

Re: [gwt-contrib] Re: Deploying to org.gwtproject.* groupId

On Friday, November 17, 2017 at 5:37:59 PM UTC+1, Thomas Broyer wrote: > > > > On Friday, November 17, 2017 at 4:11:18 PM UTC+1, Colin Alworth wrote: >> >> Sounds like there is enough diversity of opinion that this discussion >> should go on - first step seems to be deciding if we think the CLA