Author: kwin
Date: Fri Oct  7 08:04:16 2016
New Revision: 1763693

URL: http://svn.apache.org/viewvc?rev=1763693&view=rev
Log:
add missing )

Modified:
    sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext

Modified: 
sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext?rev=1763693&r1=1763692&r2=1763693&view=diff
==============================================================================
--- 
sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext 
(original)
+++ 
sling/site/trunk/content/documentation/bundles/jcr-installer-provider.mdtext 
Fri Oct  7 08:04:16 2016
@@ -6,7 +6,7 @@ The JCR installer provider scans the JCR
 
 The JCR installer provider can be configured with weighted paths which are 
scanned. By default, the installer scans in */apps* and */libs* where artifacts 
found in */apps* get a higher priority. The installer does a deep scan and uses 
a regular expression to detect folders containing artifacts to be installed. By 
default, artifacts from within a folder named *install* are provided to the 
OSGi installer.
 
-If such an install folder contains a binary artifact (e.g. a bundle or a 
config file as described in [Configuration Installer 
Factory]({{refs.configuration-installer-factory.path}}) this is provided to the 
OSGi installer. 
+If such an install folder contains a binary artifact (e.g. a bundle or a 
config file as described in [Configuration Installer 
Factory]({{refs.configuration-installer-factory.path}})) this is provided to 
the OSGi installer. 
 
 In addition every node of type *sling:OsgiConfig* is provided as a 
configuration to the installer. This has the advantage of leveraging the JCR 
structure better than binary files, but has the known limitations outlined in 
[SLING-4183](https://issues.apache.org/jira/browse/SLING-4183) and 
[SLING-2477](https://issues.apache.org/jira/browse/SLING-2477), therefore it is 
recommended to stick to one of the binary formats described in [Configuration 
Installer Factory]({{refs.configuration-installer-factory.path}}).
 


Reply via email to