Author: buildbot
Date: Tue Jul 1 13:37:04 2014
New Revision: 914593
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:37:04 2014
@@ -1 +1 @@
-1607072
+1607073
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:37:04 2014
@@ -104,16 +104,20 @@ Server definition</p>
<h2 id="server-configuration">Server configuration</h2>
<p>The server will appear in the servers view. You can double-click on it to
review the settings which were automatically provided.</p>
<p>There are a couple of important settings in the server definition page:</p>
-<h1 id="port-used-for-connecting-to-the-server">port: used for connecting to
the server</h1>
-<h1
id="publishing-interval-controls-how-fast-the-resources-will-be-published-after-a-change-we-recommend-setting-the-interval-to-0-for-fast-deploy-times">publishing
interval: controls how fast the resources will be published after a change. We
recommend setting the interval to 0, for fast deploy times</h1>
-<h1
id="username-password-context-path-controls-the-connection-details-to-the-sling-instance">username,
password, context path: controls the connection details to the Sling
instance.</h1>
-<h1 id="debug-port-used-for-connecting-in-debug-mode">debug port: used for
connecting in debug mode</h1>
+<ul>
+<li>port: used for connecting to the server</li>
+<li>publishing interval: controls how fast the resources will be published
after a change. We recommend setting the interval to 0, for fast deploy
times</li>
+<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>You can now connect to the server</p>
<h2 id="content-sync">Content sync</h2>
<p>Content projects are required to have at least</p>
-<h1
id="a-jcr_root-directory-which-contains-the-serialized-content-of-the-repository">a
jcr_root directory, which contains the serialized content of the
repository</h1>
-<h1
id="a-meta-infvaultfilterxml-file-which-contains-the-workspace-filter-definition">a
META-INF/vault/filter.xml file, which contains the workspace filter
definition</h1>
+<ul>
+<li>a jcr_root directory, which contains the serialized content of the
repository</li>
+<li>a META-INF/vault/filter.xml file, which contains the workspace filter
definition</li>
+</ul>
<p>All changes performed in the local workspace are synchronized to the
repository, given that they are included in the workspace filter definition.</p>
<h3 id="creating-a-new-content-project">Creating a new content project</h3>
<p>Creating a new Sling content project is easily done by using the new Sling
Content Project Wizard. To kick off, start by selected File -> New ->
Project and select Sling Content Project under the Sling category.</p>
@@ -153,19 +157,23 @@ Server definition</p>
<p>Additional information can be obtained by enabling the Eclipse platform
tracing facility. To do so, open the Eclipse preferences and navigate to
General -> Tracing. Make sure that 'Enable tracing' is checked and all
options under 'Sling IDE Tooling' are enabled.</p>
<p>Why do I get an errror about "No DS descriptor found at..."?</p>
<p>Bundle deployment assumes that the OSGi bundle is packaged into the
project's output directory. This includes:</p>
-<h1 id="the-manifest">the manifest</h1>
-<h1 id="compiled-class-files">compiled class files</h1>
-<h1 id="resources">resources</h1>
-<h1 id="declarative-services-descriptors">Declarative Services descriptors</h1>
+<ul>
+<li>the manifest</li>
+<li>compiled class files</li>
+<li>resources</li>
+<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>
<h1 id="known-issues">Known issues</h1>
<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>
-<h1
id="sling-3586-publishing-content-fails-if-intermediate-nodes-are-not-present-in-the-repository-the-workaround-is-to-manually-create-the-missing-nodes-in-the-repository"><a
href="https://issues.apache.org/jira/browse/SLING-3586";>SLING-3586 -
Publishing content fails if intermediate nodes are not present in the
repository</a> . The workaround is to manually create the missing nodes in the
repository .</h1>
-<h1
id="sling-3591-unable-to-delete-all-nodes-of-a-full-coverage-aggregate-the-workaround-is-to-manually-delete-the-child-nodes"><a
href="https://issues.apache.org/jira/browse/SLING-3591";>SLING-3591 - Unable to
delete all nodes of a full coverage aggregate</a> . The workaround is to
manually delete the child nodes .</h1>
-<h1
id="sling-3573-local-resources-which-are-no-longer-present-in-the-repository-are-not-deleted-when-importing-the-workaround-is-to-manually-delete-the-workspace-files"><a
href="https://issues.apache.org/jira/browse/SLING-3573";>SLING-3573 - Local
resources which are no longer present in the repository are not deleted when
importing</a> . The workaround is to manually delete the workspace files .</h1>
-<h1
id="sling-3644-improve-handling-of-binary-properties-outside-ntfile-file-nodes-currently-there-is-no-workaround-but-in-practice-this-is-not-an-often-encountered-situation"><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.</h1>
+<ul>
+<li><a href="https://issues.apache.org/jira/browse/SLING-3586";>SLING-3586 -
Publishing content fails if intermediate nodes are not present in the
repository</a> . The workaround is to manually create the missing nodes in the
repository .</li>
+<li><a href="https://issues.apache.org/jira/browse/SLING-3591";>SLING-3591 -
Unable to delete all nodes of a full coverage aggregate</a> . The workaround is
to manually delete the child nodes .</li>
+<li><a href="https://issues.apache.org/jira/browse/SLING-3573";>SLING-3573 -
Local resources which are no longer present in the repository are not deleted
when importing</a> . The workaround is to manually delete the workspace files
.</li>
+<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. 1607072 by rombert on Tue, 1 Jul 2014 13:35:08 +0000
+ Rev. 1607073 by rombert on Tue, 1 Jul 2014 13:36:58 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
