Re: GWT and Bazel

On Saturday, December 17, 2016 at 9:56:16 PM UTC+1, Konstantin Solomatov wrote:

It has dev mode, but it works only with the source folders from the module where you declare gwt_application. Are there any ways to workaround this implementation.

From the documentation there's a java_roots attribute to gwt_application (but generally with Bazel you'd put everything into a single source root, contrary to many other build tools like Maven or Gradle)

I've seen it. But it seems to be a little bit of a hack.

It is.

 

I wonder, how do you do this in google, i.e. with google's native tools? I bet, it's very hard to put everything into one source root, especially in large projects.

This is basically what packages are for. In jetpad, you've "duplicated" your (Maven) module structure into your package hierarchy, so you can easily flatten everything into a single source root and keep the exact same module separation, where one package == one module.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.