Yep, I only recently published these rules from what we were using at my company, so they're definitely immature but do work for us in a reasonably large GWT application. I'm not sure how many other people are using them yet but I'm actively maintaining them if people run into any issues.
Thomas is correct that java_roots is probably what you want - I added an example at your bug report at https://github.com/bazelbuild/rules_gwt/issues/8. It's true that it's somewhat hackish - the fact that GWT essentially contains its own internal build system can make integrating it with Bazel a little awkward. Google doesn't use these rules internally, but they do in fact keep the entirety of their code base in a single source tree. They published a paper describing it at http://cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext and there's a Wired article on it at https://www.wired.com/2015/09/google-2-billion-lines-codeand-one-place/. On Thursday, December 15, 2016 at 12:36:22 PM UTC-8, Konstantin Solomatov wrote: > > Does anybody use rules for bazel from here: > https://github.com/bazelbuild/rules_gwt? It seems that these rules are > quite immature. Does anybody try to use it? Are there any alternatives to > this? > > 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. I know that google internally has gwt rules. Do they work > in the same way or do they manage to load all source folders somehow? > > Thanks, > Kostya > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
