On Tue, Mar 24, 2009 at 10:51 PM, Vitali Lovich <vlov...@gmail.com> wrote:
> Also, this happens on every launch regardless of whether or not code was > actually changed. > Right, currently hosted mode builds TypeOracle and other things from source, so it has to run all the source through JDT each time you start it. > Sorry, my mistake. Refreshing isn't actually slow. But if it's doing a > bytecode compile, why is it even taking any time on the initial startup when > there was no source code change & the compiled classes haven't changed? > Shouldn't it notice this & not do anything? > It should not be recompiling any classes that haven't changed, but until very recently it always compiled the output of generators. Amit checked in a patch in the past week to avoid the recompile if the generator produces the same output. Eventually, we might build in a way for generators to specify their dependencies (or to automatically infer them) and not even run the generator if its dependencies have not changed, but right now that is not possible. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
