svn commit: r982714 - in /websites/staging/sling/trunk/content: ./ news/sling-ide-tooling-1.1-released.html

[bu...@apache.org]

Author: buildbot
Date: Mon Mar 14 08:43:20 2016
New Revision: 982714

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/news/sling-ide-tooling-1.1-released.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Mar 14 08:43:20 2016
@@ -1 +1 @@
-1734887
+1734889

Modified: websites/staging/sling/trunk/content/news/sling-ide-tooling-1.1-released.html
==============================================================================
--- websites/staging/sling/trunk/content/news/sling-ide-tooling-1.1-released.html (original)
+++ websites/staging/sling/trunk/content/news/sling-ide-tooling-1.1-released.html Mon Mar 14 08:43:20 2016
@@ -123,12 +123,12 @@ h2:hover > .headerlink, h3:hover > .head
 <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="../document/development/ide-tooling/new-server.png" /></p>
+<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>
 <h1 id="automatic-configuration-of-debug-classpath-based-on-the-bundles-deployed-on-the-server">Automatic configuration of debug classpath based on the bundles deployed on the server<a class="headerlink" href="#automatic-configuration-of-debug-classpath-based-on-the-bundles-deployed-on-the-server" title="Permanent link">&para;</a></h1>
 <p>When first connecting to a Sling instance, 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>Since a first source bundle resolution can potentially take a long time, this behaviour can be disabled from the server configuration page.</p>
-<p><img alt="Debugging" src="../document/development/ide-tooling/debug.png" /></p>
+<p><img alt="Debugging" src="../documentation/development/ide-tooling/debug.png" /></p>
 <h1 id="maven-configurator-for-content-package-projects">Maven configurator for content-package projects<a class="headerlink" href="#maven-configurator-for-content-package-projects" title="Permanent link">&para;</a></h1>
 <p>Maven projects configured using the <code>com.day.jcr.vault:content-package-maven-plugin</code> are now automatically configured as content projects, removing the need to manually add the needed facets after importing them into Eclipse for the first time.</p>
 <h1 id="other-minor-improvements">Other minor improvements<a class="headerlink" href="#other-minor-improvements" title="Permanent link">&para;</a></h1>
@@ -138,7 +138,7 @@ h2:hover > .headerlink, h3:hover > .head
 <li>When connecting to a server, all support bundles are automatically installed</li>
 </ul>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1734887 by rombert on Mon, 14 Mar 2016 08:41:21 +0000
+        Rev. 1734889 by rombert on Mon, 14 Mar 2016 08:43:11 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project