You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2015/11/17 14:54:02 UTC

svn commit: r972699 - in /websites/staging/sling/trunk/content: ./ documentation/development/ide-tooling.html

Author: buildbot
Date: Tue Nov 17 13:54:01 2015
New Revision: 972699

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/documentation/development/ide-tooling.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 17 13:54:01 2015
@@ -1 +1 @@
-1714579
+1714784

Modified: websites/staging/sling/trunk/content/documentation/development/ide-tooling.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/ide-tooling.html (original)
+++ websites/staging/sling/trunk/content/documentation/development/ide-tooling.html Tue Nov 17 13:54:01 2015
@@ -146,7 +146,11 @@ h2:hover > .headerlink, h3:hover > .head
 <li>username, password, context path: controls the connection details to the Sling instance.</li>
 <li>debug port: used for connecting in debug mode</li>
 </ul>
-<p>For working with OSGi bundles, a special support bundle must be installed to support fast bundle redeployment. If it is not present, you can install it using the hyperlink from the Install section.</p>
+<p>For working with OSGi bundles there are two options as to how they are installed to the Sling launchpad instance:</p>
+<ul>
+<li>Install via bundle upload: this is the normal way which creates a bundle (jar) locally and uploads that to the server. It thus works locally or remotely.</li>
+<li>Install directly from local directory: this is a faster bundle redeployment variant which does not build a bundle (jar) locally but instead instructs the server to install a bundle based on an exploded directory. (See <a href="https://issues.apache.org/jira/browse/SLING-3019">SLING-3019</a> for details). This requires a special support bundle to be present on the server. If it is not present, you can install it using the hyperlink from the Install section. Note that this only works locally since the server will directly read from the exploded directory.</li>
+</ul>
 <p><img alt="Servers Definition" src="ide-tooling/server-definition.png" /></p>
 <p>You can now connect to the server.</p>
 <h2 id="content-sync">Content sync<a class="headerlink" href="#content-sync" title="Permanent link">&para;</a></h2>
@@ -225,7 +229,7 @@ h2:hover > .headerlink, h3:hover > .head
 <li><a href="https://issues.apache.org/jira/browse/SLING-3644">SLING-3644 - Improve handling of binary properties outside nt:file file nodes</a> . Currently there is no workaround, but in practice this is not an often-encountered situation.</li>
 </ul>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1663219 by rombert on Mon, 2 Mar 2015 09:00:36 +0000
+        Rev. 1714784 by stefanegli on Tue, 17 Nov 2015 13:53:40 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project