svn commit: r1709009 - /sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext

[ro...@apache.org]

Author: rombert
Date: Fri Oct 16 14:17:43 2015
New Revision: 1709009

URL: http://svn.apache.org/viewvc?rev=1709009&view=rev
Log:
SLING-5103 - Update launchpad documentation

Update description for the Sling 8 release.

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext?rev=1709009&r1=1709008&r2=1709009&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/the-sling-launchpad.mdtext Fri Oct 16 14:17:43 2015
@@ -137,36 +137,18 @@ The *Launchpad Base* projects creates th
 
 To build a very basic Sling launcher, the *Launchpad Base* is actually all you need. But to really glue this together and get a usable system, some more work is required. Lets see how the additionaly projects *Launchpad Bundles*, *Launchpad App*, and *Launchpad WebApp* get to that.
 
-
-### Launchpad Bundles
-
-The second project we want to look at is the *Launchpad Bundles* project. This is a very simple project in that it only collects together a number of OSGi bundles, which will make up the final application. The bundles are stored in a (big) Java Archive in folders whose path is formed with `resources/9` where `9` is a start level which is assigned to the bundles as they are installed. The special start level `0` instructs the installer to not actually assign a specific start level to the bundles contained in that folder.
-
-Currently the following start level assignement is used by the *Launchpad Bundles* project:
-
-| Start Level | Bundle Group | Bundle(s) |
-|--|--|--|
-| 1 | Basic bundles required for the correct operation of Sling | org.apache.sling.commons.log
-| 5 | Apache Felix Web Console | org.apache.felix.bundlerepository, org.apache.felix.webconsole, org.apache.sling.extensions.threaddump |
-| 10 | OSGi Compendium Service Implementations | org.apache.felix.configadmin, org.apache.felix.eventadmin, org.apache.felix.metatype, org.apache.felix.scr |
-| 15 | JCR Repository (Jackrabbit) | commons-collections, commons-io-1.4.jar, commons-lang, jackrabbit-api, jackrabbit-jcr-commons, org.apache.sling.commons.mime, org.apache.sling.commons.osgi, org.apache.sling.jcr.api, org.apache.sling.jcr.base, org.apache.sling.jcr.jackrabbit.server, org.apache.sling.jcr.webdav |
-| 0 | Actual Sling Application bundles | org.apache.sling.adapter, org.apache.sling.api, org.apache.sling.bundleresource.impl, org.apache.sling.commons.json, org.apache.sling.engine, org.apache.sling.extensions.apt.parser, org.apache.sling.extensions.apt.servlet, org.apache.sling.httpauth, org.apache.sling.jcr.classloader, org.apache.sling.jcr.contentloader, org.apache.sling.jcr.ocm, org.apache.sling.jcr.resource, org.apache.sling.launchpad.content, org.apache.sling.samples.path-based.rtp, org.apache.sling.scripting.api, org.apache.sling.scripting.core, org.apache.sling.scripting.javascript, org.apache.sling.scripting.jsp, org.apache.sling.scripting.jsp.taglib, org.apache.sling.servlets.get, org.apache.sling.servlets.post, org.apache.sling.servlets.resolver |
-
-
-
 ### Launchpad App and Launchpad WebApp
 
 The *Launchpad App* and *Launchpad WebApp* bundles are actually projects which just glue together artifacts from the Launchpad projects. There is nothing special about them. Here's what is done:
 
 * Take the appropriate secondary artifact from the *Launchpad Base* project: *app* for the Standalone Java Application or *webapp* for the Web Application and unpack
 * Take the *Launchpad Base* primary artifact and place it under the name `org.apache.sling.launchpad.base.jar` into the `resources` folder
-* Take the *Launchpad Bundles* artifact and unpack it
+* Copies the list of artifacts defined in the [Provisioning model]({{refs.slingstart.path}}) 
 * Finally pack all together into a single big JAR or WAR file
 
-The artifacts can be configured to use different JCR repository implementations, based on the value of the `-Dsling.run.modes` property. The following run modes are available for the 8-SNAPSHOT version of the Sling Launchpad:
+The artifacts can be configured to use different JCR repository implementations, based on the value of the `-Dsling.run.modes` property. The following run modes are available for the 8 version of the Sling Launchpad:
 
-* `jackrabbit` ( default ): configures and starts up an Apache Jackrabbit 2.x JCR repository implementation
 * `oak`: configures and starts up an Apache Jackrabbit Oak repository implementation with a SegmentNodeStore ( TarMK ) implementation
 * `oak,oak_mongo`: configures and starts up an Apache Jackrabbit Oak repository implementation with a DocumentNodeStore implementation connected to a MongoDB database. The default configuration points to a MongoDB instance at mongodb://localhost:27017 and a database named sling.
 
-That's it. The resulting artifact may be directly used to launch the Standalone Java Application or may directly be deployed into any Servlet API 2.4 (or later) compliant servlet container.
+That's it. The resulting artifact may be directly used to launch the Standalone Java Application or may directly be deployed into any Servlet API 3.0 (or later) compliant servlet container.