Put goog.requires in HTML, so that symbols are loaded in the right order
response to code review
The etag bug is fixed for real! woo.
Merge pull request #23 from Medium/nick-etag-patch

The etag bug is fixed for real! woo.
Merge pull request #13 from nicks/nick-patch-requires

Put goog.requires in HTML, so that symbols are loaded in the right order
Removing the closure files; will replace with submodules
Moves to pulling closure from submodules of upstream git repo
Changes to make plovr build with vanilla upstream closure build dependencies
Got soyweb serving along with JS compilation; GSS not working yet
Refactoring serve "web" directory to use the same server config class everywhere
Merging my local change to closure templates upstream
Serve 304 status codes to Chrome
Cache files that are part of closure library.

Also just go back to serving -1 content length because the Sun HttpExchange class won't do 304 response with content-length 0.
Upgrade to Guava 17; Do not serve etags on cacheable responses
Move to my versions of the closure repos for now
Serve an etag in all cases
Always use the current working directory as the root path.

This fixes a bunch of problems with source maps. This means
that all files in the config.js file should be relative to the working
directory (and not have "./"" prefixes). Without this change, a path like
"/home/user/foo/bar/baz/../../../blah" will have names that show up in
sourcemaps as URLs that cannot possibly exist, like
"/input/myconfig/../../../blah".

Remove the caching response header change because it doesn't work. When you
refresh your browser your client is going to send cache-control: no-cache
because it was a forced reload. So the caching headers only really help if you
randomly navigate to your plovr server, not the standard dev workflow.
Update to local branch of my closure-templates dependency
Restore the behavior of not serving 304s to Chrome; it really does not work!
Gzip encode all responses; force the charset to utf-8