Author: rombert
Date: Tue Jul 1 13:36:58 2014
New Revision: 1607073
URL: http://svn.apache.org/r1607073
Log:
IDE tooling - correct list syntax
Modified:
sling/site/trunk/content/documentation/development/ide-tooling.mdtext
Modified: sling/site/trunk/content/documentation/development/ide-tooling.mdtext
URL:
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/ide-tooling.mdtext?rev=1607073&r1=1607072&r2=1607073&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/ide-tooling.mdtext
(original)
+++ sling/site/trunk/content/documentation/development/ide-tooling.mdtext Tue
Jul 1 13:36:58 2014
@@ -28,10 +28,10 @@ The server will appear in the servers vi
There are a couple of important settings in the server definition page:
-# port: used for connecting to the server
-# publishing interval: controls how fast the resources will be published after
a change. We recommend setting the interval to 0, for fast deploy times
-# username, password, context path: controls the connection details to the
Sling instance.
-# debug port: used for connecting in debug mode
+* port: used for connecting to the server
+* publishing interval: controls how fast the resources will be published after
a change. We recommend setting the interval to 0, for fast deploy times
+* username, password, context path: controls the connection details to the
Sling instance.
+* debug port: used for connecting in debug mode
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.
@@ -41,8 +41,8 @@ You can now connect to the server
Content projects are required to have at least
-# a jcr_root directory, which contains the serialized content of the repository
-# a META-INF/vault/filter.xml file, which contains the workspace filter
definition
+* a jcr_root directory, which contains the serialized content of the repository
+* a META-INF/vault/filter.xml file, which contains the workspace filter
definition
All changes performed in the local workspace are synchronized to the
repository, given that they are included in the workspace filter definition.
@@ -122,10 +122,10 @@ Why do I get an errror about "No DS desc
Bundle deployment assumes that the OSGi bundle is packaged into the project's
output directory. This includes:
-# the manifest
-# compiled class files
-# resources
-# Declarative Services descriptors
+* the manifest
+* compiled class files
+* resources
+* Declarative Services descriptors
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.
@@ -133,7 +133,7 @@ One often-occuring situation is that a M
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:
-# [SLING-3586 - Publishing content fails if intermediate nodes are not present
in the repository](https://issues.apache.org/jira/browse/SLING-3586) . The
workaround is to manually create the missing nodes in the repository .
-# [SLING-3591 - Unable to delete all nodes of a full coverage
aggregate](https://issues.apache.org/jira/browse/SLING-3591) . The workaround
is to manually delete the child nodes .
-# [SLING-3573 - Local resources which are no longer present in the repository
are not deleted when
importing](https://issues.apache.org/jira/browse/SLING-3573) . The workaround
is to manually delete the workspace files .
-# [SLING-3644 - Improve handling of binary properties outside nt:file file
nodes](https://issues.apache.org/jira/browse/SLING-3644) . Currently there is
no workaround, but in practice this is not an often-encountered situation.
\ No newline at end of file
+* [SLING-3586 - Publishing content fails if intermediate nodes are not present
in the repository](https://issues.apache.org/jira/browse/SLING-3586) . The
workaround is to manually create the missing nodes in the repository .
+* [SLING-3591 - Unable to delete all nodes of a full coverage
aggregate](https://issues.apache.org/jira/browse/SLING-3591) . The workaround
is to manually delete the child nodes .
+* [SLING-3573 - Local resources which are no longer present in the repository
are not deleted when
importing](https://issues.apache.org/jira/browse/SLING-3573) . The workaround
is to manually delete the workspace files .
+* [SLING-3644 - Improve handling of binary properties outside nt:file file
nodes](https://issues.apache.org/jira/browse/SLING-3644) . Currently there is
no workaround, but in practice this is not an often-encountered situation.
\ No newline at end of file
