This is a good place for an experiment, since in practice, very few people build the plugins.
The bigger picture is that we don't particularly like BUILD files that call ant, since they slow down builds for everyone at Google. There's no reason to rebuild every GWT app and run all the tests because one Java file in gwt.user changed that most people don't even use. Outside Google, people seem to prefer Maven, and I expect we won't want to use that internally either. So I'd like to see if we can just build GWT code directly. If Google can move away from ant and open source moves to Maven, we'll end up with two independent build systems instead of three that are intertwined. (Or four, if you count the plugin Makefiles. But I doubt we can get rid of those.) - Brian On Mon, Sep 17, 2012 at 11:45 AM, <j...@jaet.org> wrote: > So why not do it in the BUILD file the same way the rest of GWT does, > which also doesn't have a java directory? > > http://gwt-code-reviews.appspot.com/1834803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
