Author: buildbot
Date: Wed Apr  4 16:19:15 2012
New Revision: 811506

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 Wed Apr  4 16:19:15 2012
@@ -1 +1 @@
-1309148
+1309478

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 
Wed Apr  4 16:19:15 2012
@@ -20,7 +20,7 @@
 -->
   <link rel="shortcut icon" href="/images/RAVE-favicon.ico" 
type="image/x-icon" />
   <link href="/css/rave.css" rel="stylesheet" type="text/css">
-  <title></title>
+  <title>Managing Static Resources</title>
   <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 </head>
 
@@ -64,9 +64,8 @@
   </div>
 
   <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>, 
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>
+    <h1 class="title">Managing Static Resources</h1>
+    <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>


Reply via email to