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 2014/10/18 00:49:48 UTC
svn commit: r926142 - in /websites/staging/sling/trunk/content: ./
documentation/development/ documentation/development/ide-tooling/
Author: buildbot
Date: Fri Oct 17 22:49:48 2014
New Revision: 926142
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
websites/staging/sling/trunk/content/documentation/development/ide-tooling/new-bundle-project-step-2.png
websites/staging/sling/trunk/content/documentation/development/ide-tooling/new-bundle-project-step-4.png
websites/staging/sling/trunk/content/documentation/development/ide-tooling/new-content-project-step-3.png
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 17 22:49:48 2014
@@ -1 +1 @@
-1632670
+1632684
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 Fri Oct 17 22:49:48 2014
@@ -119,13 +119,12 @@
<p>There are a couple of important settings in the server definition page:</p>
<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><img alt="Servers Definition" src="ide-tooling/server-definition.png" /></p>
-<p>You can now connect to the server</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>
<ul>
@@ -138,9 +137,10 @@
<p><img alt="New content project step 1" src="ide-tooling/new-content-project-step-1.png" /></p>
<p>You will then be asked to name the project and select its location.</p>
<p><img alt="New content project step 2" src="ide-tooling/new-content-project-step-2.png" /></p>
-<p>Finally, you can select whether to add the project to an existing server or create a new one.</p>
+<p>Finally, you can select whether to add the project to an existing server, create a new one, or leave it undeployed.</p>
<p><img alt="New content project step 3" src="ide-tooling/new-content-project-step-3.png" /></p>
-<p>Once you press finish, the project will be created and deployed to the server.</p>
+<p>Once you press finish, the project will be created and deployed to the server if needed.</p>
+<p>Note that deploying a project on the server publishes all the resources from the project if the server is started. If the server is stopped, you need to manually publish the changes after startup.</p>
<h3 id="converting-existing-projects">Converting existing projects</h3>
<p>To mark a project as being a Sling content module, click it in the Project Explorer and Select Configure -> Convert to Sling Content Project... . A dialog will pop up and will ask you to confirm the inferred location of the jcr_root directory. You can also change this from the project properties, the Sling page.</p>
<h3 id="content-navigator">Content navigator</h3>
@@ -169,9 +169,9 @@
<p><img alt="New bundle project step 2" src="ide-tooling/new-bundle-project-step-2.png" /></p>
<p>You will be asked to configure the archetype's properties.</p>
<p><img alt="New bundle project step 3" src="ide-tooling/new-bundle-project-step-3.png" /></p>
-<p>Finally, you can select whether to add the project to an existing server or create a new one.</p>
+<p>Finally, you can select whether to add the project to an existing server, create a new one, or leave it undeployed.</p>
<p><img alt="New bundle project step 4" src="ide-tooling/new-bundle-project-step-4.png" /></p>
-<p>Once you press finish, the project will be created and deployed to the server.</p>
+<p>Once you press finish, the project will be created and deployed to the server if needed.</p>
<h3 id="converting-existing-projects_1">Converting existing projects</h3>
<p>To mark a project as being a Sling bundle module, right click it in the Project Explorer and Select Configure -> Convert to Sling Bundle Project... . A dialog will appear with all the candidate Sling bundle project from the workspace so that you can quickly select multiple projects.</p>
<h3 id="deploying-projects-on-the-server_1">Deploying projects on the server</h3>
@@ -197,13 +197,12 @@
<h2 id="known-issues">Known issues</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>
-<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>
+<li><a href="https://issues.apache.org/jira/browse/SLING-4069">SLING-4069 - Intermediate resources that do not match the filter are not created when publishing</a> . The workaround is to create the prerequisite parent nodes manually</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1612309 by rombert on Mon, 21 Jul 2014 15:13:37 +0000
+ Rev. 1632684 by rombert on Fri, 17 Oct 2014 22:49:39 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project
Modified: websites/staging/sling/trunk/content/documentation/development/ide-tooling/new-bundle-project-step-2.png
==============================================================================
Binary files - no diff available.
Modified: websites/staging/sling/trunk/content/documentation/development/ide-tooling/new-bundle-project-step-4.png
==============================================================================
Binary files - no diff available.
Modified: websites/staging/sling/trunk/content/documentation/development/ide-tooling/new-content-project-step-3.png
==============================================================================
Binary files - no diff available.