If I understand what you are saying correctly, then what you describe is expected. I think this *might* have changed in GWT 1.7, but I'm not entirely sure.
If you have one large module then at most all of your code will be compiled (i.e., translated) once. However, let's say you have 10 modules and 3 entry points. If all 3 entry points share, say, 3 common modules, then those common modules will need to be recompiled for each entry point. Does this make sense? On Dec 9, 9:28 am, soc <[email protected]> wrote: > Hi, > > I'm currently spliting up my code base (since it has gotten qute > large) and i have found something odd, that i was wondering if someone > could clarify? > > I have multiple java projects with GWT modules in each. I then build > these into a jar (around 8-9 seperate jars) that can be added to my > main GWT application's classpath and inherited in the gwt.xml > descriptor file. > > When i use this approach the compile time is anything up to 200+ > second but if i bundle all the code into my main app it compiles in > less than 40? Even with the localWorkers flags set i can't get it > below 200 seconds. I've tried compiling for one browser only and some > other optimizations but i still can't match the single projects speed > in compilation. I thought it my be a compiler linking performance > issue? > > info: GWT 1.7.1 -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
