HI David, On Thu, 2018-04-26 at 11:54 +0100, David Bosschaert wrote: > Hi all, > > > Over the past weeks a lot of work went into improving the Feature > Model in > the Sling Whiteboard codebase and trying to find the module structure > for > that would hopefully be stable going forward. > > > Right now the following modules are part of the Feature Model: > > * feature - The Feature Model API > > * feature-analyser - Analyser Module for Features > > * feature-applicationbuilder - Command line tool for building > Applications > from Features > > * feature-io - Deals with reading and writing features to disk > > * feature-karaf - Turn Features into Karaf Features > > * feature-launch - Launch a Feature-based application > > * feature-modelconverter - Convert between Features and the Sling > Provisioning Model > > * feature-resolver - Resolve Features and contents, can compute > ordering > > * osgifeature-maven-plugin - Similar to slingstart-maven-plugin but > then > for features (maybe this one should be renamed, e.g. > slingfeature-maven-plugin?) > > > Note that the feature-support is not in the list. This has been > removed. > > > With the current state I would propose that we start looking at > moving the > Feature Model into mainstream Sling. Would everyone be ok with this?
+1 from me. > > > I guess that would mean a separate Git repository for each component > in the > above list. Is there a document describing how to this is done? See https://cwiki.apache.org/confluence/display/SLING/Using+Git+with+Sling The Kibble part is not mandatory, but nice-to-have - we're not using the statistics yet. Robert > > > Best regards, > > > David
