Author: buildbot
Date: Tue Jul 1 13:46:18 2014
New Revision: 914595
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 Jul 1 13:46:18 2014
@@ -1 +1 @@
-1607076
+1607078
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 Jul 1 13:46:18 2014
@@ -95,8 +95,8 @@
Installation</p>
<h2 id="overall-concepts">Overall concepts</h2>
<p>The Sling IDE tooling is centered around the Server and Module concepts. A
Server is an instance of a Sling launchpad - or derivatives such as Adobe CQ -
on which you deploy your content. A Module is a collection of resources grouped
into a single Eclipse project which can be deployed onto one or multiple
Servers.</p>
-<p>The tooling supports content and bundle modules. Content modules typically
hold Sling scripts - like JSP and ESP files, client-side resources like CSS and
JSS file, but also arbitrary repository content. Content modules support
support setting JCR properties for nodes other than nodes and files, based on
the FileVault serialization format. You can read mode about FileVault at the
Apache Jackkrabit FileVault docs Bundle modules represent a single OSGi bundle.
-Server definition</p>
+<p>The tooling supports content and bundle modules. Content modules typically
hold Sling scripts - like JSP and ESP files, client-side resources like CSS and
JSS file, but also arbitrary repository content. Content modules support
support setting JCR properties for nodes other than nodes and files, based on
the FileVault serialization format. You can read mode about FileVault at the <a
href="https://jackrabbit.apache.org/filevault/";>Apache Jackkrabit FileVault
docs</a>. Bundle modules represent a single OSGi bundle.</p>
+<h3 id="server-definition">Server definition</h3>
<p>To create a new Sling launchpad server you will need to start a Sling
launchpad outside of Eclipse. We do not yet support starting Sling Launchpad
instances from Eclipse.</p>
<p>To kick off, create a new Sling Server using the File -> New ->
Other... menu entry.</p>
<p><img alt="New Server" src="ide-tooling/new-server.png" /></p>
@@ -134,7 +134,7 @@ Server definition</p>
<p>In the Project Explorer view there is an additional 'jcr_root' contribution
to the project. It is denoted by a folder icon with a small web overlay. This
contribution provides a logical view over the repository content, taking into
account JCR metadata. As such, .content.xml files will be folded into the
corresponding node.</p>
<p>Node properties can be edited in a distinct JCR properties view.</p>
<h3 id="filterxml-workspace-filter-definition">filter.xml - workspace filter
definition</h3>
-<p>A content project does not synchronize all its contents to the workspace.
Instead, it looks for a filter.xml file which defines which content is included
in synchronization operations. More information about the filter.xml file
format and semantics can be found at FileVault docs - Workspace Filter</p>
+<p>A content project does not synchronize all its contents to the workspace.
Instead, it looks for a filter.xml file which defines which content is included
in synchronization operations. More information about the filter.xml file
format and semantics can be found at <a
href="https://jackrabbit.apache.org/filevault/filter.html";>FileVault docs -
Workspace Filter</a>.</p>
<h3 id="deploying-projects-on-the-server">Deploying projects on the server</h3>
<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>After content projects are deployed, each change will cause the changed
resources to be updated in the repository.</p>
@@ -177,7 +177,7 @@ Server definition</p>
<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. 1607076 by rombert on Tue, 1 Jul 2014 13:43:37 +0000
+ Rev. 1607078 by rombert on Tue, 1 Jul 2014 13:46:09 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
