You may also want to check out plovr: http://code.google.com/p/plovr/
The basic idea is that you create a config file that identifies the
directories where your Soy and JS files live, as well as the Compiler
options that you want to use when compiling. As explained on the
Getting Started page (http://code.google.com/p/plovr/wiki/
GettingStarted), you can run plovr in either "server" mode or "build"
mode with the config file. In server mode, your JS and Soy are
dynamically recompiled every time you load a URL, so you can use that
URL in a <script> tag for fast development. In build mode, you just
run plovr with a config file and it prints the compiled version (of
whatever you've configured) to standard out.
An example of plovr running in server mode is at (take a loop at the
<script> tag loaded by the page): http://plovr.org/demo/advanced-demo.html
And you can see the size breakdown of what is being compiled at:
I fixed a number of bugs and added a lot of new features over the
weekend. The documentation is pretty light at this point, but it's
there! As mentioned on the roadmap (http://code.google.com/p/plovr/
wiki/Roadmap), I'm planning to expose more compiler options and add
support for modules in the (hopefully near) future.