> Do you have a step by step guide to run the closure compiler externally ? >
Basically you would need to replicate what has been done programmatically in the removed ClosureJsRunner class. See commit https://github.com/gwtproject/gwt/commit/162ccc9c9112a09bf9ea046da95760f5f1886b72 Looks like you have to - define your own gwt_externs file to tell Closure Compiler which special GWT variables not to rename - maybe create a hack.js file that exports gwtOnLoad function so it does not get removed by Closure Compiler. Maybe its not needed if also passing in the <module>.nocache.js file to Closure compiler. no idea. - Give Closure Compiler the GWT output (your *.cache.js files including split points) in the correct ordering as split point files have dependencies (initial fragment, leftover, split points) -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
