Please send your member requests with some background information on why
you need early access.

On Fri, Jun 1, 2018 at 3:08 PM Julien Dramaix <[email protected]>
wrote:

> I changed the permission settings. You should now be able to apply for
> membership at https://groups.google.com/forum/#!forum/j2cl-external
>
> -Julien
>
> On Fri, Jun 1, 2018 at 1:50 PM Alberto Mancini <[email protected]>
> wrote:
>
>> Hello Goktug,
>> thanks a lot for the opportunity.
>> Actually seems that the address [email protected] does not
>> exist.
>> ---- [email protected] ----
>> We're writing to let you know that the group you tried to contact
>> (j2cl-external) may not exist, or you may not have permission to post
>> messages to the group. A few more details on why you weren't able to post:
>>
>>  * You might have spelled or formatted the group name incorrectly.
>>  * The owner of the group may have removed this group.
>>  * You may need to join the group before receiving permission to post.
>>  * This group may not be open to posting.
>> ----- -----
>>
>> It is just me, I'm not autrorized or actually the address is spelled
>> incorrectly?
>>
>> Thanks,
>>    Alberto.
>>
>>
>> On Thu, May 31, 2018 at 11:51 PM 'Goktug Gokdogan' via GWT Contributors <
>> [email protected]> wrote:
>>
>>> Hi all.
>>>
>>> Sorry for the delays in getting J2CL work for opensource. Some of the
>>> delays were out of our control but this is something we actively working on
>>> in the last few months and having progress. In the meantime plenty of
>>> active GWT contributors already has access to it for a long time and
>>> working on getting GWT 3 ready. Also a while back, I said "if there are
>>> more people who needs access to J2CL for GWT 3 porting, we can give them
>>> access" but it is not usable for average developer.
>>>
>>> If you think you need earlier access to J2CL in as-is state (which
>>> partially builds with plenty of workarounds), pls send a message to
>>> [email protected]; and pls make your case (e.g. porting X
>>> from GWT 2 SDK to GWT 3) and we will give access. However we cannot help
>>> you a lot at the moment when you hit problems (you will) so pls set your
>>> expectations accordingly.
>>>
>>>
>>> On Thu, May 31, 2018 at 6:02 AM Ivan Markov <[email protected]>
>>> wrote:
>>>
>>>> Don't you think there could've been 2x or even 3x as much people
>>>> working on porting GWT2 stuff over to J2CL if J2CL was released in the
>>>> first place? For one, releasing J2CL could've made me reconsider how much
>>>> time I invest in my own SDBG pet project. Which - at the current situation
>>>> is exactly zero. Or whether to invest time in the abandoned typescript2java
>>>> effort, which would bring seamless JSInterop with gazillions of .d.ts'd JS
>>>> libraries without the need to manually code JSInterop bindings...
>>>>
>>>> Say what you want, but 3 months since my original rant that at the top
>>>> of this thread, the "basic Bazel building issues" of Goktug seem still to
>>>> be a roadblock and J2CL is still nowhere to be seen.
>>>>
>>>> ... and then we had Daniel planning to write a book on J2CL end of
>>>> 2016, remember? Come on guys, it is Q3 2018 now... I might now agree with
>>>> Learner Evermore on his points 2) to 5), but with point 1) he nailed it:
>>>> "1. The backing company backed off but kept the crucial new piece
>>>> secret - J2CL."
>>>>
>>>>
>>>> On Wednesday, May 30, 2018 at 6:07:25 PM UTC+3, Frank Hossfeld wrote:
>>>>>
>>>>> That's not really true. There are a lot of people working on the GWT
>>>>> module, getting them out of GWT and moving them to standalone artifacts.
>>>>> Doing that, they replace JSNI with JsInterop, replace generators, etc. 
>>>>> This
>>>>> is all done, to get GWT 2 ready for GWT 3. And if you want to see 
>>>>> something
>>>>> existing in GWT 3, you can ask vertispan to do the job.
>>>>>
>>>>> With the knowledge about the things, that will change with GWT 3 /
>>>>> J2CL, I was able to make mvp4g ready for GWT 3 / J2CL. I replaced the
>>>>> generator with APT and remove the dependency to any GWT classes. I created
>>>>> a sample application based on the new version (mvp4g2) and Elemental 2. 
>>>>> And
>>>>> yes, it works with J2CL.
>>>>>
>>>>> And, keep in mind, applications written in GWT in 2010 still work.
>>>>> What was the favorite JS framework at that time? I don't remember.
>>>>>
>>>> --
>>>> 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
>>>> [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/03d79d23-11e5-423b-9009-d439a569c512%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/03d79d23-11e5-423b-9009-d439a569c512%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> 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 [email protected]
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA2Z333EfYXk-RAD_%3DPJkrXV62JkfWHJFrwTdUsj%3DZ_StA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA2Z333EfYXk-RAD_%3DPJkrXV62JkfWHJFrwTdUsj%3DZ_StA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30VkKJ3gLvv2NupBDKXNXqTY0trxCYsQ%2BM6NoNRh92mtfUQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30VkKJ3gLvv2NupBDKXNXqTY0trxCYsQ%2BM6NoNRh92mtfUQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6%2BJ3Bk2bN1-aHMp1z4Sh%3Dv9-pxa21L%3D9AT_gSMj24z5Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6%2BJ3Bk2bN1-aHMp1z4Sh%3Dv9-pxa21L%3D9AT_gSMj24z5Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA1CC%2BVXrhfOH5vZ9Pkq8V%2B6SHeUwsfOraAZihp5YTQyHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to