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

[bu...@apache.org]

Author: buildbot
Date: Thu Dec  3 14:42:38 2015
New Revision: 974405

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 Dec  3 14:42:38 2015
@@ -1 +1 @@
-1717650
+1717776

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 Dec  3 14:42:38 2015
@@ -142,7 +142,24 @@ Each run mode is associated with a set o
 <h3 id="start-levels">Start Levels<a class="headerlink" href="#start-levels" title="Permanent link">&para;</a></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. 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<a class="headerlink" href="#artifacts" title="Permanent link">&para;</a></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>
+<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. For a plain jar the text definition for an artifact is:</p>
+<div class="codehilite"><pre>            <span class="n">groupId</span><span class="o">/</span><span class="n">artifactId</span><span class="o">/</span><span class="n">version</span>
+            <span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">sling</span><span class="o">/</span><span class="n">api</span><span class="o">/</span>2<span class="p">.</span>8<span class="p">.</span>0
+</pre></div>
+
+
+<p>If you want to specify the type, it's appended after the version:</p>
+<div class="codehilite"><pre>            <span class="n">groupId</span><span class="o">/</span><span class="n">artifactId</span><span class="o">/</span><span class="n">version</span><span class="o">/</span><span class="n">type</span>
+            <span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">sling</span><span class="o">/</span><span class="n">api</span><span class="o">/</span>2<span class="p">.</span>8<span class="p">.</span>0<span class="o">/</span><span class="n">jar</span>
+</pre></div>
+
+
+<p>If you want to specify the classifier, it gets appended after the type:</p>
+<div class="codehilite"><pre>            <span class="n">groupId</span><span class="o">/</span><span class="n">artifactId</span><span class="o">/</span><span class="n">version</span><span class="o">/</span><span class="n">type</span><span class="o">/</span><span class="n">classifier</span>
+            <span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">sling</span><span class="o">/</span><span class="n">api</span><span class="o">/</span>2<span class="p">.</span>8<span class="p">.</span>0<span class="o">/</span><span class="n">jar</span><span class="o">/</span><span class="n">test</span>
+</pre></div>
+
+
 <h3 id="configurations">Configurations<a class="headerlink" href="#configurations" title="Permanent link">&para;</a></h3>
 <p>A configuration has a pid, or a factory pid and an alias and of course the properties of the configuration object.</p>
 <p>Special configurations can be marked with a leading ":" of the pid. Special configurations are not added to the OSGi config admin. There are some predefined special configurations</p>
@@ -345,7 +362,7 @@ Each run mode is associated with a set o
 <span class="nt">&lt;/plugin&gt;</span>
 </pre></div>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1706489 by rombert on Fri, 2 Oct 2015 21:16:51 +0000
+        Rev. 1717776 by cziegeler on Thu, 3 Dec 2015 14:42:23 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project