Re: [gwt-contrib] The elusive J2CL

2018-03-08 Thread 'Goktug Gokdogan' via GWT Contributors
The main blocker for releasing J2CL for wider audience is even basic missing functionalities around building it in open-source and seeing at least some output for your compilations. That is blocked on missing functionalities in bazel. After that we can probably finished in more timely manner. There

Re: [gwt-contrib] The elusive J2CL

2018-03-08 Thread Ivan Markov
Goktug, We don't want a polished experience. We want *some* experience. :) Is there anything we can help with? BTW, I thought Bazel is already open sourced and you are already building with it? What's the roadblock there? BTW 2: Releasing a J2CL binary would also help, as long as that's somehow

Re: [gwt-contrib] The elusive J2CL

2018-03-08 Thread Nándor Előd Fekete
I am *really* interested. Can you sign me up? On Thursday, March 8, 2018 at 9:13:01 AM UTC+1, Goktug Gokdogan wrote: > > The main blocker for releasing J2CL for wider audience is even basic > missing functionalities around building it in open-source and seeing at > least some output for your com

Re: [gwt-contrib] The elusive J2CL

2018-03-08 Thread Alberto Mancini
Hello, yes, definitely I would like to be in. I am really interested. Cheers, Alberto. On Thu, Mar 8, 2018 at 2:21 PM Nándor Előd Fekete wrote: > I am *really* interested. Can you sign me up? > > > On Thursday, March 8, 2018 at 9:13:01 AM UTC+1, Goktug Gokdogan wrote: >> >> The main blocker

Re: [gwt-contrib] The elusive J2CL

2018-03-08 Thread 'Goktug Gokdogan' via GWT Contributors
> There is still tone of work to do for a polished open source experience but at least we can give access to more people who is really interested. What I meant here; is giving access *after* basic bazel stuff is finished so there will be something to play with. We don't want to give access to a br