> > I've noticed that if I enable the closure compiler the -compileReport flag > is totaly ignored and the soycReport in the extra folder is missing. > > Someone has a workaround? >
Not yet, but you can compile once without closure compiler to see whats going on during compile and then compile it again with closure compiler and check the generated files to see size differences: - war/<permutation strong name>.html - war/<modulename>/deferredjs/<permutation strong name>/<splitpoint>.cache.js (one of these files is the left over fragment..it should be the one with the highest number that does not match any split point number) Also when you use -XfragmentMerge for the new code split algorithm it seems like the compile report shows 0 bytes for left over fragment which is clearly wrong (at least in our case here). So don't jump up and be happy if you see 0 bytes for left over ;-) -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ZBxB_-v72MkJ. 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.
