You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sling.apache.org by ro...@apache.org on 2013/04/28 16:15:02 UTC

svn commit: r1476779 - /sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext

Author: rombert
Date: Sun Apr 28 14:15:02 2013
New Revision: 1476779

URL: http://svn.apache.org/r1476779
Log:
SLING-2658 -  Document that the bundle list does not allow selection of
the HttpService provider 

Modified:
    sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext

Modified: sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext?rev=1476779&r1=1476778&r2=1476779&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext (original)
+++ sling/site/trunk/content/documentation/development/maven-launchpad-plugin.mdtext Sun Apr 28 14:15:02 2013
@@ -86,6 +86,8 @@ The bundle list file uses a simple XML s
 
 Within each `bundle` element, `type` and `classifier` are also supported.
 
+The Http Service support can not be configured using the bundle list, but only using the `jarWebSupport` parameter, since it is specific to whether the Sling Launchpad is built as a java application (in which case the Jetty-based Http Service is used) or a web application (in which case the Http Service bridge is used).
+
 ## Artifact Definition
 
 The `defaultBundleList`, `jarWebSupport`, `additionalBundles`, and `bundleExclusions` parameters are configured with artifact definitions. This is done using a syntax similar to Maven dependency elements: