Author: buildbot
Date: Thu Apr 25 19:20:12 2013
New Revision: 859907

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Apr 25 19:20:12 2013
@@ -1 +1 @@
-1475909
+1475911

Modified: 
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
==============================================================================
--- 
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
 (original)
+++ 
websites/staging/sling/trunk/content/documentation/bundles/jcr-installer-provider.html
 Thu Apr 25 19:20:12 2013
@@ -103,7 +103,7 @@
 * JCR installer provider (<a 
href="http://svn.apache.org/repos/asf/sling/trunk/installer/providers/jcr";>org.apache.sling.jcr.jcrinstall</a>)</p>
 <p>To watch the logs produced by these modules, you can filter 
<code>sling/logs/error.log</code> using <code>egrep 
'jcrinstall|osgi.installer'</code>.</p>
 <h2 id="install-and-remove-a-bundle">Install and remove a bundle</h2>
-<p>We'll use the <a 
href="http://www.knopflerfish.org/releases/2.0.5/jars/desktop*awt/desktop*awt_all-2.0.0.jar";>Knopflerfish
 Desktop</a> bundle for this example, it is convenient as it displays a 
graphical user interface when started.</p>
+<p>We'll use the <a 
href="http://www.knopflerfish.org/releases/2.0.5/jars/desktop_awt/desktop_awt_all-2.0.0.jar";>Knopflerfish
 Desktop</a> bundle for this example, it is convenient as it displays a 
graphical user interface when started.</p>
 <p>We use <code>curl</code> to create content, to make it easy to reproduce 
the example by copying and pasting the <code>curl</code> commands. Any other 
way to create content in the repository will work, of course.</p>
 <p>By default, JCRInstall picks up bundles found in folders named 
<em>install</em> under <code>/libs</code> and <code>/apps</code>, so we start 
by creating such a folder:</p>
 <div class="codehilite"><pre><span class="n">curl</span> <span 
class="o">-</span><span class="n">X</span> <span class="n">MKCOL</span>  <span 
class="n">http:</span><span class="sr">//</span><span 
class="n">admin:admin</span><span class="nv">@localhost:8888</span><span 
class="sr">/apps/</span><span class="n">jcrtest</span>
@@ -193,7 +193,7 @@
 </ul>
 <p>Many of these tests are fairly readable, and can be used to find out in 
more detail how these modules work.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; 
text-align: right;">
-        Rev. 1475862 by dklco on Thu, 25 Apr 2013 17:28:38 +0000
+        Rev. 1475911 by dklco on Thu, 25 Apr 2013 19:20:06 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache 
Sling project


Reply via email to