Re: [gwt-contrib] Re: Generator and Linker maintenance and changes

2016-05-09 Thread Predrag Pesic
Great post Colin. You are "the voice of the people" here. I couldn't agree more with the statement: "Finally, if we are *to be serious about this*, as a GWT user, contributor, and steering committee member, I have to expect to see usable solutions in the *near future* to move away from these too

[gwt-contrib] Re: Upgrade bundled jetty to 9.2.16.v20160414

2016-05-09 Thread Thomas Broyer
On Monday, May 9, 2016 at 7:51:45 AM UTC+2, Alexander Leshkin wrote: > > воскресенье, 8 мая 2016 г., 23:07:37 UTC+3 пользователь Thomas Broyer > написал: >> >> Not sure I understand your concern: Jetty is no longer bundled in gwt-dev >> in 2.8.0-SNAPSHOT (Maven artifacts only) > > > I mean gwt-

[gwt-contrib] Re: Upgrade bundled jetty to 9.2.16.v20160414

2016-05-09 Thread Alexander Leshkin
OK, I understood. Thank you. понедельник, 9 мая 2016 г., 11:29:06 UTC+3 пользователь Thomas Broyer написал: > > > > On Monday, May 9, 2016 at 7:51:45 AM UTC+2, Alexander Leshkin wrote: >> >> воскресенье, 8 мая 2016 г., 23:07:37 UTC+3 пользователь Thomas Broyer >> написал: >>> >>> Not sure I un

Re: [gwt-contrib] Re: Generator and Linker maintenance and changes

2016-05-09 Thread Thomas Broyer
On Monday, May 9, 2016 at 5:39:36 AM UTC+2, Colin Alworth wrote: > > Thanks everyone. Since we don't really have much of a consensus on this, > perhaps we can take some middle ground here? > > I certainly agree that we want people to move away from generators in > general, though without finish

[gwt-contrib] Re: Configurable checks for GWT

2016-05-09 Thread Jens
Sometimes I am not sure if we should use a normal or a critical check. Basically my understanding is that we should use a normal check if the code would also fail (but obviously with a JS error instead of a required Java Exception) with an error if the check was not present. If the code would f

Re: [gwt-contrib] Re: Configurable checks for GWT

2016-05-09 Thread 'Goktug Gokdogan' via GWT Contributors
Thanks for asking; I think I never explained this well. This is mostly judgement call but in general the rule of thumb is: - Assume no checks as the starting point - Look at the code and see what will happen if we don't have the check: - If the missing check will leave the object in a very brok

Re: [gwt-contrib] Setting up gwt project for development

2016-05-09 Thread 'John Stalcup' via GWT Contributors
Konstantin: You're correct that internally we use Blaze (which is open sourced as Bazel at http://bazel.io/) and not Ant. But even though most of our BUILD files (the build configuration that Blaze uses) are included in the open source repo, some significant pieces are missing (some referenced sc

Re: [gwt-contrib] Setting up gwt project for development

2016-05-09 Thread Michael Zhou
I filed https://github.com/bazelbuild/bazel/issues/1077 and it looks like Bazel will include support for gwt_application. On Monday, May 9, 2016 at 2:59:36 PM UTC-4, John Stalcup wrote: > > Konstantin: > > You're correct that internally we use Blaze (which is open sourced as > Bazel at http://ba

Re: [gwt-contrib] Re: Configurable checks for GWT

2016-05-09 Thread Jens
Hm ok, I think I got it. I would say my Arrays.sort() example should actually use a critical check then because array.slice() can do lots unexpected things (negative indexes for either argument works but results an unexpected subset of array items to be sorted, toIndex can be larger than fromIn

Re: [gwt-contrib] Re: Configurable checks for GWT

2016-05-09 Thread 'Goktug Gokdogan' via GWT Contributors
On Mon, May 9, 2016 at 12:52 PM, Jens wrote: > Hm ok, I think I got it. I would say my Arrays.sort() example should > actually use a critical check then because array.slice() can do lots > unexpected things (negative indexes for either argument works but results > an unexpected subset of array it