On Monday, January 16, 2017 at 10:29:01 AM UTC+1, Jens wrote: > > > And please, Gradle ;) >
J2Cl itself will likely be built with Bazel (given that even Dagger et al. are moving from Maven to Bazel, I don't think we want to invest in maintaining a non-Bazel build –contributed by "the community"– in parallel to Bazel –contributed by Google–), and our goal as a community will be to help Google distribute it on Central. Calling J2Cl from Gradle should be a no-brainer. As for GWT 3, if you ask me, it'd be a "rebuild", using either Bazel or Gradle, rather than an evolution of the current repo. I'll probably leave it to someone else to build a Maven plugin for using GWT 3, unless my existing plugin works out-of-the-box (depends what tooling GWT 3 will provide), but would happily contribute to a Gradle plugin (the hardest part actually is deciding on a "standard" project layout; this should be done by a specific "working group", not unilaterally by an individual). -- 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/7f03d2b8-d4ba-4a89-9443-a69df148d121%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
