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

[bu...@apache.org]

Author: buildbot
Date: Mon Mar 14 08:55:55 2016
New Revision: 982716

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 Mon Mar 14 08:55:55 2016
@@ -1 +1 @@
-1734892
+1734893

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 Mon Mar 14 08:55:55 2016
@@ -232,6 +232,21 @@ h2:hover > .headerlink, h3:hover > .head
 <p>To deploy a project on the server, open the Servers view and use the Add and Remove... dialog to add one or more modules.</p>
 <p><img alt="Add and Remove projects from server" src="ide-tooling/add-remove-projects.png" /></p>
 <p>After OSGi bundle projects are deployed, each change will cause the bundle to be redeployed on the server.</p>
+<h2 id="sightly-support">Sightly support<a class="headerlink" href="#sightly-support" title="Permanent link">&para;</a></h2>
+<p><em>Available with Sling IDE Tooling for Eclipse 1.1 or newer</em></p>
+<p>Sightly support has been added through an additional, optional, feature named <em>Sling IDE Tools - Sightly Integration</em>.</p>
+<p>This feature provides the following enhancements:</p>
+<ul>
+<li>auto-completion of tag named and attributes names in the HTML Editor</li>
+<li>wizards for creating new Sightly scripts and Use Classes ( Java and Javascript )</li>
+<li>Sightly-aware validation for HTML files</li>
+</ul>
+<p><img alt="Sightly Editor" src="ide-tooling/sightly-editor.png" /></p>
+<p>These enhancements are enabled once the Sightly facet is added to a project. This is done automatically when converting a project to content project, but can also be done manually via the project properties, under the <em>Project Facets</em> page.</p>
+<h2 id="debugging">Debugging<a class="headerlink" href="#debugging" title="Permanent link">&para;</a></h2>
+<p>When first connecting to a Sling instance in debug mode, the IDE tooling tries to bind all the sources associated with the bundles deployed on the server and retrieves the associated source artifacts using Maven. Therefore, the debug classpath is as close as possible to sources used to build the bundles deployed on the server.</p>
+<p><img alt="Debugging" src="ide-tooling/debug.png" /></p>
+<p>Since a first source bundle resolution can potentially take a long time, this behaviour can be disabled from the server configuration page.</p>
 <h2 id="troubleshooting">Troubleshooting<a class="headerlink" href="#troubleshooting" title="Permanent link">&para;</a></h2>
 <h3 id="gathering-debug-information">Gathering debug information<a class="headerlink" href="#gathering-debug-information" title="Permanent link">&para;</a></h3>
 <p>All operations that are performed on the Sling launchpad are logged in the Sling console. To view these operations, open the Eclipse console view and select Open Console -&gt; Sling Console.</p>
@@ -248,21 +263,6 @@ h2:hover > .headerlink, h3:hover > .head
 <li>Declarative Services descriptors</li>
 </ul>
 <p>One often-occuring situation is that a Maven project using the maven-scr-plugin generates the descriptors outside of target/classes, typically in target/scr-plugin-generated. To fix this, make sure that you're using the maven-scr-plugin 1.15.0 or newer and that you have not set a custom outputDirectory.</p>
-<h2 id="sightly-support">Sightly support<a class="headerlink" href="#sightly-support" title="Permanent link">&para;</a></h2>
-<p><em>Available with Sling IDE Tooling for Eclipse 1.1 or newer</em></p>
-<p>Sightly support has been added through an additional, optional, feature named <em>Sling IDE Tools - Sightly Integration</em>.</p>
-<p>This feature provides the following enhancements:</p>
-<ul>
-<li>auto-completion of tag named and attributes names in the HTML Editor</li>
-<li>wizards for creating new Sightly scripts and Use Classes ( Java and Javascript )</li>
-<li>Sightly-aware validation for HTML files</li>
-</ul>
-<p><img alt="Sightly Editor" src="../documentation/development/ide-tooling/sightly-editor.png" /></p>
-<p>These enhancements are enabled once the Sightly facet is added to a project. This is done automatically when converting a project to content project, but can also be done manually via the project properties, under the <em>Project Facets</em> page.</p>
-<h2 id="debugging">Debugging<a class="headerlink" href="#debugging" title="Permanent link">&para;</a></h2>
-<p>When first connecting to a Sling instance in debug mode, the IDE tooling tries to bind all the sources associated with the bundles deployed on the server and retrieves the associated source artifacts using Maven. Therefore, the debug classpath is as close as possible to sources used to build the bundles deployed on the server.</p>
-<p><img alt="Debugging" src="../documentation/development/ide-tooling/debug.png" /></p>
-<p>Since a first source bundle resolution can potentially take a long time, this behaviour can be disabled from the server configuration page.</p>
 <h2 id="known-issues">Known issues<a class="headerlink" href="#known-issues" title="Permanent link">&para;</a></h2>
 <p>The content sync implementation tries to mimic the FileVault semantics as closely as possible. However, it is possible that some more exotic content structures will not be handled properly. Some of the problems we're are of are:</p>
 <ul>
@@ -270,7 +270,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. 1734892 by rombert on Mon, 14 Mar 2016 08:54:00 +0000
+        Rev. 1734893 by rombert on Mon, 14 Mar 2016 08:55:47 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project