Are all your modules actually producing JavaScript you are going to run? If not then you don't need to GWT compile those?
To do the clever optimisation GWT does it looks at the source for all the client code. So I don't think you would save a lot re-structuring (if you really need to produce JavaScript each time). On Wednesday, December 11, 2013 4:00:36 PM UTC, Beatriz Nombela wrote: > > Hi! > > I'm trying to reduce the compile time of a GWT project on jenkins. My > project structure can be summarized to the following one: > > - module_1: jar and GWT module > - module_2: multimodule maven project, each submodule is a jar, and each > one contains a GWT module. Each GWT module inherits from module_1 > - module_3: war, contains a GWT module that inherits from module_2 > > The problem with this structure is the moment when everything is compiled > on jenkins: > - module_1 compiles > - module_2 compiles, and accordingly module_1 is compiled again > - module_3 compiles, and accordingly each submodule in module_2 is > compiled, and at the same time module_1 is compiled again some more times > > My goal is to avoid recompiling some of the modules so many times. I'd > like to know whether the GWT modules are well structured or not, so I could > focus on restructuring GWT modules or in Jenkins side. > > Thanks in advance! > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
