We got it mostly working. Hopefully you should get an announcement soon. On Tue, Oct 23, 2018 at 10:06 AM Konstantin Solomatov < [email protected]> wrote:
> Are there any updates on J2CL? A lot of time has passed. > > On Friday, June 15, 2018 at 3:54:08 AM UTC-4, Julien Dramaix wrote: >> >> > 2. J2CL itself is build with Bazel (for the reasons you mentioned). >> This would not matter much, *as long as you could push the J2CL >> artifacts to Maven Central in an automated (Bazel) pipeline*. *Can Bazel >> do that*? >> >> Yes it can. We are already building jsinterop-base and Elemental2 with >> Bazel and push artifact on Maven Central. >> >> -Julien >> >> On Thu, Jun 14, 2018 at 3:50 PM Hristo Stoyanov <[email protected]> >> wrote: >> >>> Guys, >>> Thanks for the update to J2CL! Here is what I understood, the questions >>> I have - correct me, if I am wrong: >>> >>> 1. Google is seeing good results from J2CL in a number of products, so >>> your internal funding won't be cut, J2CL won't be abandoned! That is good >>> news! >>> >>> 2. J2CL itself is build with Bazel (for the reasons you mentioned). This >>> would not matter much, *as long as you could push the J2CL artifacts to >>> Maven Central in an automated (Bazel) pipeline*. *Can Bazel do that*? >>> >>> 3. Some GWT folks are developing Gradle and Maven plug-ins. *What is >>> the status of those*? I think this is the most important thing - once >>> the J2CL jars are in Maven central and the plug-ins ready, people can start >>> building apps with J2CL? >>> >>> 4. This comment from Goktug: ..."*we use some tools that does code >>> pruning during build which helps some with the performance, and those tools >>> are not available for open source. Something we will eventually look at but >>> not very soon" worries me. Is J2CL a 100% Java or you use other stuff that >>> can not be released?* >>> >>> >>> *5. I still don't quite understand why not dump everything J2CL on Gihub >>> "AS IS" and let us sort it out?* >>> >>> >>> *Also, It would be helpful if some of the developers who already >>> received the J2CL code drop comment and clarify what needs to be finished >>> from their point of view.* >>> >>> >>> *As far as GWT3, I don't understand what is the value of it at all, >>> maybe valuable time/resources can be spent on J2CL instead, once it is >>> placed on Github* >>> >>> >>> >>> *Thanks. * >>> >>> -- >>> 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/807613cc-5945-49c1-8f5e-205dd53f5dea%40googlegroups.com >>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/807613cc-5945-49c1-8f5e-205dd53f5dea%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/d4af467b-ae98-4ab6-a665-d465c5145527%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/d4af467b-ae98-4ab6-a665-d465c5145527%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%3DyUA260YR-MCguZadyrsQB3_vxhDCCsB7tW10OVmwn6%2BWi7g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
