This preview adds one special feature: a development-mode-only file system
cache for compiled CoffeeScript. Using this cache, you can avoid
re-compilation of CoffeeScript source files that haven't changed since the
prior execution, which means much faster page loads for CoffeeScript-heavy
pages.

Configure the  tapestry.compiled-asset-cache-dir  symbol to control where
to place the cache files (otherwise, they end up in the default temporary
directory).  Example:

-Dtapestry.compiled-asset-cache-dir=build/compiled-asset-cache

When Tapestry needs to compile CoffeeScript source file into JavaScript, it
checks this directory; if it finds a matching file in the cache directory,
it simply uses the contents of the file and bypasses the actual
compilation. This means that when restarting the application, most (or all)
of your CoffeeScript sources will be ready and waiting as JavaScript.

This is only enabled for development mode; in production, Tapestry assumes
that all resources are static.

This preview is available from the Maven repository at:

https://repository.apache.org/content/repositories/orgapachetapestry-154/


-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

Reply via email to