Author: buildbot
Date: Tue Apr 3 21:01:16 2012
New Revision: 811365
Log:
Staging update by buildbot for rave
Modified:
websites/staging/rave/trunk/content/ (props changed)
websites/staging/rave/trunk/content/documentation/manage-static-resources.html
Propchange: websites/staging/rave/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 3 21:01:16 2012
@@ -1 +1 @@
-1309144
+1309148
Modified:
websites/staging/rave/trunk/content/documentation/manage-static-resources.html
==============================================================================
---
websites/staging/rave/trunk/content/documentation/manage-static-resources.html
(original)
+++
websites/staging/rave/trunk/content/documentation/manage-static-resources.html
Tue Apr 3 21:01:16 2012
@@ -66,12 +66,12 @@
<div id="content">
<h1 class="title"></h1>
<p><strong>Managing Static Resources</strong></p>
-<p>Apache Rave uses <a href="http://code.google.com/p/wro4j/";>wro4j</a> to
optimize JavaScript. At build time it uses Google Closure Compiler to
concatenate and minify all of the individual Rave javascript files into one
file called rave_all.min.js</p>
-<p>All of the original JavaScript files, along with the minified version, are
bundled into the WAR. Rave uses a Portal Preference to determine if it should
serve out the individual source files, or the single optimized file. By
default, for ease of debugging, Rave serves out the individual scripts. Rave
admins can change the Portal Preference, called javaScriptDebugMode, to
"Disabled" if they want to serve out the optimized file (recommended for
production installations).<br />
+<p>Apache Rave uses <a href="http://code.google.com/p/wro4j/";>wro4j</a>,
specifically the wro4j-maven-plugin, to optimize JavaScript. At build time it
uses Google Closure Compiler to concatenate and minify all of the individual
Rave javascript files into one file called rave_all.min.js</p>
+<p>All of the original JavaScript files, along with the minified version, are
bundled into the WAR. During run-time Rave uses a Portal Preference to
determine if it should serve out the individual source files, or the single
optimized file. By default, for ease of debugging, Rave serves out the
individual scripts. Rave admins can change the Portal Preference, called
javaScriptDebugMode, to "Disabled" if they want to serve out the optimized file
(recommended for production installations).<br />
</p>
<p>Like all other Portal Preferences, changes are effective immediately,
making it useful when you need to debug an issue in a production environment.
</p>
<p><em>Settings</em></p>
-<p>Out-of-the box Rave has configured wro4j to use Google Closure Compiler
with SIMPLE_OPTIMIZATIONS. If you would like to change the JavaScript
Processor to use ADVANCED_OPTIMIZATIONS, or another library all-together (such
as YUI Compressor), you can overlay the wro.properties file located in
rave-portal-resources and modify the postProcessors. See the <a
href="http://code.google.com/p/wro4j/";>wro4j</a> website for more
information.</p>
+<p>Out-of-the box Rave has configured <a
href="http://code.google.com/p/wro4j/";>wro4j</a> to use Google Closure Compiler
with SIMPLE_OPTIMIZATIONS. If you would like to change the JavaScript
Processor to use ADVANCED_OPTIMIZATIONS, or another library all-together (such
as YUI Compressor), you can overlay the wro.properties file located in
rave-portal-resources and modify the postProcessors. See the <a
href="http://code.google.com/p/wro4j/";>wro4j</a> website for more
information.</p>
<p><em>Future Enhancements</em></p>
<p><a href="http://code.google.com/p/wro4j/";>wro4j</a> supports a wide variety
of JavaScript and CSS related optimization libraries. As we continue to
improve Rave we will look into expanding its use to CSS as well.</p>
</div>
