svn commit: r1706489 - /sling/site/trunk/content/documentation/development/slingstart.mdtext

[ro...@apache.org]

Author: rombert
Date: Fri Oct  2 21:16:51 2015
New Revision: 1706489

URL: http://svn.apache.org/viewvc?rev=1706489&view=rev
Log:
slingstart: fix syntax highlighting

Modified:
    sling/site/trunk/content/documentation/development/slingstart.mdtext

Modified: sling/site/trunk/content/documentation/development/slingstart.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/slingstart.mdtext?rev=1706489&r1=1706488&r2=1706489&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/slingstart.mdtext (original)
+++ sling/site/trunk/content/documentation/development/slingstart.mdtext Fri Oct  2 21:16:51 2015
@@ -170,9 +170,9 @@ The slingstart Maven plugin introduces t
 
 A model can reference other slingstart or slingfeature artifacts. When such an artifact is reference, the type needs to be specified, for example:
 
-   [artifacts]
-       org.apache.sling/org.apache.sling.launchpad/8-SNAPSHOT/slingstart
-       org.apache.sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/slingfeature
+    [artifacts]
+        org.apache.sling/org.apache.sling.launchpad/8-SNAPSHOT/slingstart
+        org.apache.sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/slingfeature
 
 The resulting model is a merged model, starting with the dependencies and then merging in the current model.
 
@@ -186,12 +186,12 @@ In addition, it can also remove artifact
 
 Let's look at an example base model
 
-   [artifacts]
-       my/special/artifact/1.0.0
-       commons/library/1.0.0
+    [artifacts]
+        my/special/artifact/1.0.0
+        commons/library/1.0.0
        
-   [artifacts runModes=test]
-       another/one/2.1.0
+    [artifacts runModes=test]
+        another/one/2.1.0
 
 Another model wants to use the above model as it's base but:
 
@@ -215,25 +215,25 @@ Note that the version for removal does n
 
 Configurations can be removed in the same way by just specifying their PID in the :remove run mode. This is the base model:
 
-   [configurations]
-       my.special.configuration.b
+    [configurations]
+        my.special.configuration.b
           foo="bar"
-       another.special.configuration.a
+        another.special.configuration.a
           x="y"
 
 When this model is merged with the following model, the resulting model has a different configuration for my.special.configuration.b and no configuration for another.special.configuration.a:
 
-   [configurations]
-       my.special.configuration.b
+    [configurations]
+        my.special.configuration.b
           a="b"
 
-   [configurations runModes=:remove]
-       another.special.configuration.a
+    [configurations runModes=:remove]
+        another.special.configuration.a
 
 By default if a model inherits from another and uses the same configuration pid, the configuration is overwritten! In the above example, the configuration my.special.configuration.b contains a single property named "a". It is also possible to merge configurations:
 
-   [configurations]
-       my.special.configuration.b [mode=merge]
+    [configurations]
+        my.special.configuration.b [mode=merge]
           a="b"
 
 When the merge directive is used, the configurations are merged and the properties are applied as a delta to the base configuration. Therefore the configuration my.special.configuration.b will have two properties "a" and "foo".