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

Posted to commits@sling.apache.org by cz...@apache.org on 2017/09/01 15:27:34 UTC

svn commit: r1806981 - /sling/whiteboard/cziegeler/feature/readme.md

Author: cziegeler
Date: Fri Sep  1 15:27:34 2017
New Revision: 1806981

URL: http://svn.apache.org/viewvc?rev=1806981&view=rev
Log:
Introduce builder context

Modified:
    sling/whiteboard/cziegeler/feature/readme.md

Modified: sling/whiteboard/cziegeler/feature/readme.md
URL: http://svn.apache.org/viewvc/sling/whiteboard/cziegeler/feature/readme.md?rev=1806981&r1=1806980&r2=1806981&view=diff
==============================================================================
--- sling/whiteboard/cziegeler/feature/readme.md (original)
+++ sling/whiteboard/cziegeler/feature/readme.md Fri Sep  1 15:27:34 2017
@@ -101,6 +101,8 @@ Once a feature is processed, included re
     * repoinit is just aggregated (appended)
     * artifact extensions are handled like bundles
 
+While includes must not be used for assembling an application, they provide an important concept for manipulating existing features. For example to replace a bundle in an existing feature and deliver this modified feature.
+
 # Extensions
 
 An extension has a unique name and a type which can either be text, JSON or artifacts. Depending on the type, inheritance is performed like this: