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 2015/05/07 23:22:22 UTC

svn commit: r950496 - in /websites/staging/sling/trunk/content: ./ documentation/development/slingstart.html

Author: buildbot
Date: Thu May  7 21:22:22 2015
New Revision: 950496

Log:
Staging update by buildbot for sling

Modified:
    websites/staging/sling/trunk/content/   (props changed)
    websites/staging/sling/trunk/content/documentation/development/slingstart.html

Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May  7 21:22:22 2015
@@ -1 +1 @@
-1678160
+1678263

Modified: websites/staging/sling/trunk/content/documentation/development/slingstart.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/development/slingstart.html (original)
+++ websites/staging/sling/trunk/content/documentation/development/slingstart.html Thu May  7 21:22:22 2015
@@ -116,7 +116,7 @@ Each run mode is associated with a set o
 </ul>
 <p>Other special run modes can be defined by using a single run mode name which starts with a colon, like :test. These run modes can be used by special tooling.</p>
 <h3 id="start-levels">Start Levels</h3>
-<p>Each run mode has start levels. These start levels correspond to OSGi start levels. The default start level has the level 0 and should be used for all non bundle artifacts. If a non bundle artifact is configured with a start level, it's still provisioned, however the start level information might not have any meaning.</p>
+<p>Each run mode has start levels. These start levels correspond to OSGi start levels. The default start level has the level 0 and should be used for all non bundle artifacts. If a non bundle artifact is configured with a start level, it's still provisioned, however the start level information might not have any meaning. As usually the provisioned artifacts are bundles and as start levels are pretty handy, this was conscious design decision in order to keep the model files small.</p>
 <h3 id="artifacts">Artifacts</h3>
 <p>An artifact is defined by Maven coordinates, that is group id, artifact id and version. Type and classifier can be specified, too. Type defaults to "jar". Although the maven way of referring to an artifact is used, the model is in no way tied to Maven and can be used with any tooling.</p>
 <h3 id="configurations">Configurations</h3>
@@ -266,7 +266,7 @@ In addition, it can also remove artifact
 
 <p>Note that the version for removal does not play a role, it's not compared for an exact match. Configurations can be removed in the same way by just specifying their PID in the :remove run mode.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1676994 by cziegeler on Thu, 30 Apr 2015 14:06:52 +0000
+        Rev. 1678263 by cziegeler on Thu, 7 May 2015 21:22:11 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project