This is an automated email from the ASF dual-hosted git repository.
davidb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git
The following commit(s) were added to refs/heads/master by this push:
new ec2a2e3 Remove documention that now lives on
sling-org-apache-sling-feature
ec2a2e3 is described below
commit ec2a2e3c66eacc021bbf77f65c80205c123a7624
Author: David Bosschaert <[email protected]>
AuthorDate: Fri Apr 27 12:14:30 2018 +0100
Remove documention that now lives on sling-org-apache-sling-feature
---
featuremodel/apicontroller.md | 44 -----
featuremodel/design/feature-model.json | 107 -------------
featuremodel/prototype.md | 283 ---------------------------------
featuremodel/readme.md | 8 -
featuremodel/requirements.md | 119 --------------
5 files changed, 561 deletions(-)
diff --git a/featuremodel/apicontroller.md b/featuremodel/apicontroller.md
deleted file mode 100644
index 0fb330e..0000000
--- a/featuremodel/apicontroller.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# API Controller
-
-If you're assembling a platform (in contrast to a final application) out of
several features and provide this platform for customers to build their
application on top if, an additional control of the API provided by the
platform is needed. The bundles within the features provide all kinds of APIs
but you might not want to expose all of these as extension points but rather
want to use some of it internally within either a single feature or share
within your features.
-
-This is a proposal about how to add such additional metadata to the feature
model. An API controller at runtime enforces the rules.
-
-# Visibility of API
-
-A feature exports some api, however there are different types of clients of
the API:
-
-* Bundles shipped as part of the platform
-* Application bundles using the platform
-
-We can generalize this by saying that API is either globally visible (to every
client) or only visible to features within the same context. Usually this is
referred to as a "region": The platform spawns its own region and a customer
application has its own region, too. In theory there could be several customer
applications running in the same framework on top of the platform, and each
application has its own region.
-
-Without any further information, API is globally visible by default. However,
for platform features we want the opposite as we want to ensure that newly
added API is not world-wide visible by default. Therefore we'll add an
additional build time check (analyzer) that checks that each platform feature
has an api controller configuration as below.
-
-A feature can have an additional extension JSON named regions:
-
- "regions" : {
- "region" : "platform", // name of the region
- "global-exports" : [
- "org.apache.sling.resource.api.*"
- ],
- "region-exports" : [
- "org.apache.sling.commons.scheduler"
- ]
- }
-
-In the example above the feature declares:
-
-* The name of the region it belongs to (platform)
-* The list of packages it is exporting to everyone (Sling's resource API)
-* The additional list of packages it is exporting to features within the same
region (scheduler api)
-
-Of course the above mentioned packages need to be exported by some bundle
within the feature.
-
-If the regions extension is missing, it is assumed that all packages are
exported and that the feature runs in the global region.
-
-If the region information is missing, the global region is used. If the
packages list for global-exports or local-exports is missing, it is assumed to
be all packages. If none should be exported, an empty array needs to be
specified.
-
-This model is intentionally kept simple and restricted to a feature being in
only a single region. In theory we could think of use cases where a feature is
shared across two (or more) regions, but not shared globally. However this gets
pretty complicated easily and therefore we suggest to make such features global.
-
-To support feature inheritance, a custom extension handler must be registered
which will merge the extension - if the inherited one and the target feature
use a different region, this is considered an error. If they have the same
region, the packages are merged. Of course the inheriting feature can remove
this extension before processing. In addition the extension handler must mark
each bundle with the region, otherwise this relationship gets lost later on
when the application is build.
diff --git a/featuremodel/design/feature-model.json
b/featuremodel/design/feature-model.json
deleted file mode 100644
index 4a5b49f..0000000
--- a/featuremodel/design/feature-model.json
+++ /dev/null
@@ -1,107 +0,0 @@
-{
- "#": "A key that starts with a hash is a comment",
-
- "id": "org.apache.sling:my.app:feature:optional:1.0",
-
- "# variables used in includes, requirements, capabilities and bundles
sections":
- "# are substituted at build time. Configuration and framework properties
at launch time.",
- "variables": {
- "cfgvar": "somedefault",
- "xyz-ver": "1.2.3",
-
- "#": "When converting to provisioning model, if you need a special
name",
- "provisioning.model.name": ":boot"
- },
-
- "includes": [
- {
- "id": "org.apache.sling:sling:9",
- "removals": {
- "configurations": [],
- "bundles": [],
- "framework-properties": []
- }
- }
- ],
- "requirements": [
- {
- "namespace": "osgi.contract",
- "directives": {
- "filter": "(&(osgi.contract=JavaServlet)(version=3.1))"
- }
- }
- ],
- "capabilities": [
- {
- "namespace": "osgi.implementation",
- "attributes": {
- "osgi.implementation": "osgi.http",
- "version:Version": "1.1"
- },
- "directives": {
- "uses":
"javax.servlet,javax.servlet.http,org.osgi.service.http.context,org.osgi.service.http.whiteboard"
- }
- },
- {
- "namespace": "osgi.service",
- "attributes": {
- "objectClass:List<String>":
"org.osgi.service.http.runtime.HttpServiceRuntime"
- },
- "directives": {
- "uses":
"org.osgi.service.http.runtime,org.osgi.service.http.runtime.dto"
- }
- }
- ],
-
- "framework-properties": {
- "foo": 1,
- "org.osgi.framework.storage": "${tempdir}",
- "org.apache.felix.scr.directory": "launchpad/scr"
- },
-
- "bundles": [
- {
- "id": "org.apache.sling:security-server:2.2.0",
- "hash": "4632463464363646436",
-
- "#": "This is the relative start order inside the feature",
- "start-order": 5
- },
- {
- "id": "org.apache.sling:application-bundle:2.0.0",
- "start-order": 10
- },
- {
- "id": "org.apache.sling:another-bundle:2.1.0",
-
- "#": "OSGi start level is also supported",
- "start-level": 20,
- "run-modes": ["oak-tar"],
-
- "configurations": {
- "#": "This configuration only gets applied when this bundle is
resolved",
- "org.apache.sling.somepid": {
- "dbuser": "${dbuser}",
- "dbpass": "${dbpass}"
- }
- }
- },
- "org.apache.sling:foo-xyz:${xyz-ver}"
- ],
-
- "configurations": {
- "my.pid": {
- "foo": 5,
- "bar": "${cfgvar}",
-
- "# The tempdir variable is not specified at the variables
section.":
- "# It needs to be provided at launch, otherwise the launch will
stop.",
- "tempdir": "${tempdir}",
-
- "number:Integer": 7
- },
- "my.factory.pid~name": {
- "a.value":"yeah"
- }
- }
-}
diff --git a/featuremodel/prototype.md b/featuremodel/prototype.md
deleted file mode 100644
index 76f13fd..0000000
--- a/featuremodel/prototype.md
+++ /dev/null
@@ -1,283 +0,0 @@
-# Prototype
-
-The prototype uses JSON as a well defined and understood format. This fits
nicely with the new OSGi R7 JSON format for configurations.
-
-A model file describes a feature. A feature consists of:
-* A unique id and version (see Feature Identity below)
-* A list of bundles described through maven coordinates
- * Grouped by start level (required)
- * Additional metadata like a hash etc. (optional)
- * Configurations (optional)
-* A set of global configurations
-* A set of framework properties
-* A list of provided capabilities
-* A list of required capabilities
-* A set of includes (of other features) described through maven coordinates
- * Modifications (removals) of the includes (optional)
-* Extensions (optional)
- * A list of repoinit instructions
- * A set of content packages described through maven coordinates
- * Additional metadata like a hash etc. (optional)
- * Configurations (optional)
-
-Notes for users of Apache Sling's provisioning model:
-
-* No support for run modes in the model - run modes can be modeled through
separate features
-
-# Feature Identity
-
-A feature has a unique id. Maven coordinates
(https://maven.apache.org/pom.html#Maven_Coordinates) provide a well defined
and accepted way of uniquely defining such an id. The coordinates include at
least a group id, an artifact id, a version and a type/packaging. A classifier
is optional.
-
-While group id, artifact id, version and the optional classifier can be freely
choosen for a feature, the type/packaging is defined as "osgifeature".
-
-TBD: Is "osgifeature" a good type?
-
-# Maven Coordinates
-
-Maven coordinates are used to define the feature id and to refer to artifacts
contained in the feature, e.g. bundles, content packages or other features.
There are two supported ways to write down such a coordinate:
-
-* Using a colon as a separator for the parts:
groupId:artifactId[:type[:classifier]]:version as defined in
https://maven.apache.org/pom.html#Maven_Coordinates
-* Using a mvn URL: 'mvn:' group-id '/' artifact-id [ '/' [version] [ '/'
[type] [ '/' classifier ] ] ] ]
-
-In some cases only the coordinates are specified as a string in one of the
above mentioned formats. In other cases, the artifact is described through a
JSON object. In that case, the *id* property holds the coordinates in one of
the formats.
-
-# Requirements and Capabilities vs Dependencies
-
-In order to avoid a concept like "Require-Bundle" a feature does not
explicitly declare dependencies to other features. These are declared by the
required capabilities, either explicit or implicit. The implicit requirements
are calculated by inspecting the contained bundles (and potentially other
artifacts like content packages ).
-
-Once a feature is processed by tooling, the tooling might create a full list
of requirements and capabilities and add this information in a special section
to the final feature. This information can be used by tooling to validate an
instance (see below) and avoids rescanning the binary artifacts. However this
"cached" information is optional and tooling must work without it (which means
it needs access to the binaries in that case). TBD the name and format of this
information.
-
-# Feature Header
-
-The JSON feature object has the following properties:
-
-* *id* : The feature id as described above. Defining the type is optional, if
it is not defined, it defaults to "osgifeature".
-* *title* : Optional title for the feature.
-* *description* : Optional long text description of the feature.
-* *vendor* : Optional vendor information.
-* *license* : Optional license information
-
-# Bundles
-
-The JSON feature object might contain a *bundles* property holding a JSON
array with the bundles contained in this feature. The values in this array can
either be a string holding the coordinates for the bundle or a JSON object if
additional properties need to be specified. The JSON object supports the
following properties:
-
-* *id* : The id of the bundle (maven coordinates). This property is required.
-* *start-order* : The value is an integer greater or equals to 1. This
specifies the start order of the bundle. The start-order specifies the start
order of the bundle in relation to other bundles in the feature. Bundles are
started in ascending order and stopped in descending order according to the
start-order directive values. Bundles with the same start-order value may be
started and stopped in any order in relation to each other. There is no default
value for start-order. If the start order
-is not specified then the bundle is started in any order.
-* *resolution* : The value is either "mandatory" or "optional". A mandatory
bundle needs to be satisfied; an optional bundle does not need to be satisfied.
The default value is mandatory.
-
-TBD: The implementation currently uses the map based configuration. It needs
to change.
-
-# Includes
-
-Includes allow an aggregation of features and a modification of the included
feature: each entity listed in the included feature can be removed, e.g a
configuration or a bundle. The list of includes must not contain duplicates
(not comparing the version of the includes). If there are duplicates, the
feature is invalid.
-
-Once a feature is processed, included references are removed and the content
of the included features becomes part of the current feature. The following
algorithm applies:
-
-* Includes are processed in the order they are defined in the model. The
current feature (containing the includes) is used last which means the
algorithm starts with the first included feature.
-* Removal instructions for an include are handled first
-* A clash of bundles or content packages is resolved by picking the latest
version (not the highest!)
-* Configurations will be merged by default, later ones potentially overriding
newer ones:
- * If the same property is declared in more than one feature, the last one
wins - in case of an array value, this requires redeclaring all values (if they
are meant to be kept)
- * Configurations can be bound to a bundle. When two features are merged, all
cases can occur: both might be bound to the same bundle (symbolic name), both
might not be bound, they might be bound to different bundles (symbolic name),
or one might be bound and the other one might not. As configurations are
handled as a set regardless of whether they are bound to a bundle or not, the
information of the belonging bundle is handled like a property in the
configuration. This means:
- * If the last configuration belongs to a bundle, this relationship is kept
- * If the last configuration does not belong to a bundle and has no
property removal instruction, the relationship from the first bundle is used
(if there is one)
- * If the last configuration has a property removal instruction for the
bundle relationship, the resulting configuration is unbound
-* Later framework properties overwrite newer ones
-* Capabilities and requirements are appended - this might result in
duplicates, but that doesn't really hurt in practice.
-* Extensions are handled in an extension specific way:
- * 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:
-* For type text: simple appended
-* For type JSON: merging of the JSON structure, later arriving properties
overriding existing ones
-* For type artifacts: merging of the artifacts, higher version wins
-
-# Handling of Environments
-
-A feature itself has no special support for environments (prod, test, dev). In
practice it is very unlikely that a single file exists containing
configurations for all environments, especially as the configuration might
contain secrets, credentials, urls for production services etc which are not
meant to be given out in public (or to the dev department). Instead, a separate
feature for an environment can be written and maintained by the different share
holders which adds the environment [...]
-
-# Bundles and start levels
-
-Each bundle needs to be explicitly assigned to a start level. There is no
default start level as a default start level is not defined in the OSGi spec.
In addition, it is a little bit confusing when looking at the model when there
is a list of bundles without a start level. Which start level do these have? It
is better to be explicit.
-
-However as soon as you have more than one feature and especially if these are
authored by different authors, start level handling becomes more tricky.
Assigning correct OSGi start levels in such scenarios would require to know all
features upfront. Therefore this start level information is interpret as
follows: instead of directly mapping it to a start level in the OSGi framework,
it defines just the startup order of bundles within a feature. Features are
then started in respect of their [...]
-
-# Configurations belonging to Bundles
-
-In most cases, configurations belong to a bundle. The most common use case is
a configuration for a (DS) component. Therefore instead of having a separate
configurations section, it is more intuitiv to specify configurations as part
of a bundle. The benefit of this approach is, that it can easily be decided if
a configuration is to be used: if exactly that bundle is used, the
configurations are used; otherwise they are not.
-
-However, there might be situations where it is not clear to which bundle a
configuration belongs or the configuration might be a cross cutting concern
spawning across multiple bundles. Therefore it is still possible to have
configurations not related to a particular bundle.
-
-In fact, configurations - whether they are declared as part of a bundle or not
- are all managed in a single set for a feature. See above for how includes
etc. are handled.
-
-# Example
-
-This is a feature example:
-
- {
- "id" : "org.apache.sling:my.app:feature:optional:1.0",
-
- "includes" : [
- {
- "id" : "org.apache.sling:sling:9",
- "removals" : {
- "configurations" : [
- ],
- "bundles": [
- ],
- "framework-properties" : [
- ]
- }
- }
- ],
- "requirements" : [
- {
- "namespace" : "osgi.contract",
- "directives" : {
- "filter" : "(&(osgi.contract=JavaServlet)(version=3.1))"
- }
- }
- ],
- "capabilities" : [
- {
- "namespace" : "osgi.implementation",
- "attributes" : {
- "osgi.implementation" : "osgi.http",
- "version:Version" : "1.1"
- },
- "directives" : {
- "uses" :
"javax.servlet,javax.servlet.http,org.osgi.service.http.context,org.osgi.service.http.whiteboard"
- }
- },
- {
- "namespace" : osgi.service",
- "attributes" : {
- "objectClass:List<String>" :
"org.osgi.service.http.runtime.HttpServiceRuntime"
- },
- "directives" {
- "uses" :
"org.osgi.service.http.runtime,org.osgi.service.http.runtime.dto"
- }
- }
- ],
- "framework-properties" {
- "foo" : 1,
- "brave" : "something",
- "org.apache.felix.scr.directory" : "launchpad/scr"
- },
- "bundles" : {
- "1" : [
- {
- "id" : "org.apache.sling:security-server:2.2.0",
- "hash" : "4632463464363646436"
- },
- "org.apache.sling:application-bundle:2.0.0",
- "org.apache.sling:another-bundle:2.1.0"
- ],
- "2" : [
- "org.apache.sling:foo-xyz:1.2.3"
- ]
- },
- "configurations" {
- "my.pid" {
- "foo" : 5,
- "bar" : "test",
- "number:Integer" : 7
- },
- "my.factory.pid~name" {
- "a.value" : "yeah"
- }
- }
-
-# Relation to Repository Specification (Chapter 132)
-
-There are two major differences between a repository as described in the
Repository Service Description and the feature model. A repository contains a
list of more or less unrelated resources whereas a feature describes resources
as a unit. For example a feature allows to define a bundle together with OSGi
configurations - which ensures that whenever this feature is used, the bundle
*together with* the configurations are deployed. A repository can only describe
the bundle as a separate r [...]
-
-The second difference is the handling of requirements and capabilities. While
a repository is supposed to list all requirements and capabilities of a
resource as part of the description, the feature model does not require this.
As the feature model refers to the bundle and the bundle has the requirements
and capabilities as metadata, there is no need to repeat that information.
-
-By these two differences you can already tell, that a repository contents is
usually generated by tools while a feature is usually a human created resource.
While it is possible to create a repository index out of a feature, the other
way round does not work as the repository has no standard way to define
relationships between resources.
-
-# Requirements and Capabilities of Artifacts
-
-The feature model does not allow to explicitly list requirements or
capabilities for artifacts. An artifact, for example a bundle, contains this
information as part of its metadata. However, to calculate or display these,
the tool processing the feature needs to have access to the artifact and needs
to extract this. While in general this does not pose a problem by itself, it
might happen that the same artifact is processed several times for example
during a build process, causing overhead.
-
-To avoid this, a feature might contain an additional section, named "reqscaps"
(TODO find a better name). This section is grouped by artifact ids and contains
the requirements and capabilities of each artifact. While the requirements and
capabilities of a single artifact must be correct and neither leave out or add
additional ones, the list of artifacts must not be complete. Tooling will first
look into this section to get requirements and capabilities for an artifact. If
there are none, [...]
-
- {
- ...
- "reqscaps" : {
- "org.apache.sling:org.apache.sling.scripting.jsp:1.0.0" : {
- "capabilities" : [],
- "requirements" : []
- }
- }
-
-
-# Appendix A : Provisioning Applications
-
-An application jar can contain a set of features (including the listed
artifacts).
-
-An optional application configuration further defines the possibilites:
-
- {
- "features" : [
- "org.apache.sling:org.apache.sling.launchpad:10"
- ],
- "options" : [
- "org.apache.sling:org.apache.sling.scripting.jsp:1.0.0",
- {
- "id" :
"org.apache.sling:org.apache.sling.scripting.htl:1.0.0",
- "tag": "htl"
- }
- ],
- "defaults" : {
- "auto-add-options": true,
- "tags" : ["htl"]
- },
- "framework" : {
- "id" : "org.apache.felix:org.apache.felix.framework:5.6.4"
- }
- }
-
-Such a configuration is required for an application, at least one feature
needs to be listed in either the features or the options section.
-All features listed in the features section will be added to the application,
the ones listed in options are optional and depending on the settings and user
input will either be added or left out. In addition all available features of
an application will be used to make the application runnable (resolvable).
-
-# Appendix B : Apache Sling's Provisioning Model
-
-The documentation for Apache Sling's provisioning model can be found here:
https://sling.apache.org/documentation/development/slingstart.html
-
-## Short description of Sling's provisioning model:
-
-* Text based file format, defining features (several in a single file)
-* A feature can have a name and version (both optional)
-* A feature consists of sections, well defined ones like the run modes and
user defined sections
-* A run mode has artifacts (with start levels), configurations and settings
(framework properties)
-* Variables can be used throughout a feature
-* Inheritance is supported on a feature base through artifacts
-* Configuration merging is possible
-
-## Advantages of the provisioning model
-
-* Well known by Sling developers, has been introduced some years ago. Some
tooling around it
-* Very concise, especially for defining artifacts
-* Extensible, custom sections can be added, e.g used by Sling for repoinit,
subsystem definitions, content package definitions
-* Easy diff
-* Special API with semantics related to the prov model (not a general purpose
config API)
-
-## Disadvantages of the provisioning model
-
-* Single file can contain more than one feature
-* Custom DSL - no standard format (like JSON)
-* Inheritance and custom artifacts (content packages) are mixed with bundles,
which makes processing and understanding more complicated
-* Adding additional info to artifacts looks strange
-* Two formats for configurations and now there is an official JSON based
format defined through OSGi R7
-* Strange object relationship between feature and run modes
-* API (object relation) differs from text file (to make the text format easier)
-* Tooling only available as maven plugins, not separate usable
-* Run mode handling is complicating the feature files and processing of those
-* Tightly coupled with the way Sling's launchpad works, therefore no
independent OSGi format
diff --git a/featuremodel/readme.md b/featuremodel/readme.md
deleted file mode 100644
index 63fdf65..0000000
--- a/featuremodel/readme.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# The OSGi Feature Model
-
-This project aims to define a common OSGi feature model to build an OSGi
application out of higher level modules.
-
-* [Requirements](requirements.md)
-* [Prototype](prototype.md)
-* [API Controller Proposal](apicontroller.md)
-
diff --git a/featuremodel/requirements.md b/featuremodel/requirements.md
deleted file mode 100644
index 90bdeec..0000000
--- a/featuremodel/requirements.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# An Introduction to the OSGi Feature Model
-
-Typical OSGi applications are assembled out of bundles and configured through
both, OSGi configurations and framework properties (though these are less
frequently used than OSGi configurations). Depending on the nature of the
application, there might be additional artifact types involved.
-
-While bundles already provide a good way to define rather small, coherent
modules, there is often a need to distribute or provision a set of such bundles
together with some configuration. OSGi Deployment Admin and OSGi subsystems are
two ways of trying to solve this issue. The feature model of Apache Karaf and
the provisioning model of Apache Sling are two other approaches.
-
-The established common term for such higher level modules is feature. The
goals of this proposal are:
-
-* Defining a common mechanism to describe such features.
-* Describe a common algorithm to combine features to either create higher
level features or an OSGi applications.
-
-The model is a general purpose feature model and in no way tied to Apache
Sling.
-
-# Requirements
-
-## Model Requirements
-
-The feature model is about describing a feature, aggregating features to
either build higher level features or an application. The model should meet the
following requirements:
-
-* SFM010 - The feature model should be described through a text format which
is easily consumable by both humans and machines, that can be edited with
common editors and support text-based diff operations.
-* SFM020 - A feature must be describable through a single file.
-* SFM030 - Multiple features must be described in multiple files.
-* SFM040 - The feature model language must support comments.
-* SFM050 - The feature model may support more than one text-based definition
language where the language used can be easily inferred, for example from the
file extension.
-* SFM060 - The feature model should provide support for long and multi-line
values without creating files that become hard to handle.
-* SFM070 - A feature model must have a unique identifier.
-* SFM080 - A feature model must have a version.
-* SFM090 - A feature model must be referenceable through Apache Maven
coordinates.
-* SFM100 - It must be possible to specify the bundles belonging to the
feature, including version.
-* SFM110 - It must be possible to specify the bundles in a feature in terms of
Apache Maven coordinates.
-* SFM120 - The feature model must allow the specification of the order in
which the bundles inside the feature are started. This should be relative to
when the feature itself is started.
-* SFM130 - It must be possible to define whether a bundle is mandatory or
optional.
-* SFM140 - It must be possible to associate any additional metadata like a
hash with a bundle.
-* SFM150 - It must be possible to specify the OSGi configurations for a
feature.
-* SFM160 - Both normal OSGi configurations as well as factory configurations
must be supported. The feature model must support all data types supported by
the OSGi Configuration Admin specification.
-* SFM170 - The OSGi configuration resource format as defined in the OSGi
Configurator Specification must be supported.
-* SFM180 - It must be possible to associate an OSGi configuration with a
bundle within a feature. If the bundle is not resolved at runtime then the
associated configuration also does not get installed.
-* SFM190 - It must be possible to define framework properties.
-* SFM200 - The feature model must be extensible to allow other artifacts than
bundles.
-* SFM210 - It must be possible to specify the artifacts in a feature in terms
of Apache Maven coordinates.
-* SFM220 - It must be possible to associate any additional metadata like a
hash with an artifact.
-* SFM230 - It must be possible to define whether an artifact is mandatory or
optional.
-* SFM240 - The feature model must be extensible to allow other/additional
content.
-* SFM250 - It must be possible to mark the additional content as optional.
-* SFM260 - A feature must be able to specify additional requirements and
capabilities that extend the requirements and capabilities from the contained
artifacts.
-* SFM270 - A feature must be able to extend other features.
-* SFM280 - A feature must be able to depend on other features through the
requirements/capabilities model based on the feature contents. The feature
model must be able to deal with circular dependencies. However, there must be
no way of explicitly requiring a feature from another feature.
-* SFM290 - The feature model must describe how several features are aggregated
to build a higher level feature. This description must include all parts of the
feature model (bundles, configurations, framework properties etc.). The
description should be general for extension, which means it should describe how
extensions are aggregated without requiring the model implementation to know
the type of extension.
-* SFM300 - The feature model must describe how several features are combined
to build an application. This description must include all parts of the feature
model (bundles, configurations, framework properties etc.). The description
should be general for extension, which means it should describe how extensions
are aggregated without requiring the model implementation to know the type of
extension.
-* SFM310 - When features are aggregated, either to create a higher level
feature or an application, and a bundle/artifact is encountered with different
versions, the feature model must be capable of only using the bundle/artifact
with the highest version number. The detection is based on the artifact/bundle
id, not the bundle symbolic name.
-* SFM320 - When features are aggregated, either to create a higher level
feature or an application, and a bundle/artifact is encountered with different
versions, the feature model must be capable of including both versions
side-by-side. The detection is based on the artifact/bundle id, not the bundle
symbolic name.
-* SFM330 - When features are aggregated, either to create a higher level
feature or an application, the resulting feature or application must be minimal
meaning it must not contain additional or unneeded artifacts.
-* SFM340 - The feature model must support controlling of the exported API as
described in
https://github.com/apache/sling-whiteboard/blob/master/featuremodel/apicontroller.md
-* SFM350 - The feature model must calculate the startup order of bundles for
an aggregated application respecting the dependencies between features and
their contents.
-* SFM360 - The feature model must support variables to be used throughout the
model, avoiding the need to repeat the same value several times.
-* SFM370 - When features are aggregated, the ordering of the processing of
those features needs to be predictable and stable.
-* SFM380 - The feature model must support adding or overwriting requirements
and capabilities of a contained bundle or artifact. This is in oder to correct
invalid metadata or to add missing metadata of the artifact.
-* SFM390 - The feature model must support adding or overwriting manifest
headers for a bundle. For example to allow to change the bundle symbolic name
or to add missing OSGi metadata to a plain jar file.
-* SFM400 - The feature model must support a textual representation for an
application aggregated out of features. The format should be as similar as
possible to the feature format.
-* SFM410 - It must be possible to specify the framework to launch an
application as part of the application model.
-* SFM420 - When features are aggregated to either a higher level feature or an
application, the resulting feature or application must still contain the
variables.
-* SFM430 - The startup order of features and bundles must be part of the
resulting aggregated application model.
-* SFM440 - The feature model must support additional, optional information
about the feature like a human readable title, a description, vendor and
licensing information.
-* SFM450 - The feature model must use a versioned descriptor format so that if
the format evolves in the future users can state in feature model files what
version they are written for.
-
-## API Requirements
-
-* SFM460 - The feature model should provide an externally accessible API for
reading and writing feature files.
-
-## Analysis Requirements
-
-* SFA010 - Tooling must be able to compute the effective requirements of a
feature by inspecting the feature's content and combining this with
requirements specified on the feature itself.
-* SFA020 - Tooling must be able to compute the capabilities of a feature by
inspecting the feature's content and directly specified capabilities.
-* SFA030 - The feature model should support to store the results of SFA010 and
SFA020 as part of the model, avoiding duplicate calculations.
-
-## Resolving Requirements
-
-* SFR010 - Tooling must be able to find all features that provide the
capabilities required by a given feature, from a set of available features.
-
-## Packaging requirements
-
-* SFP010 - Tooling must be able to convert a feature to an Apache Karaf Feature
-* SFP020 - Tooling must be able to convert a feature to an Apache Sling
Provisioning Model Archive
-* SFP030 - Tooling must be able to convert a feature to an OSGi Subsystem
-* SFP040 - Tooling should be able to create diff packages between two versions
of a features
-
-## Launching Requirements
-
-* SFL010 - Tooling must support creating an application model out of one or
more features.
-* SFL012 - Tooling must provide a way to add new features to an existing
application.
-* SFL015 - Tooling should be able to annotate the application model by stating
for each element what its origin is.
-* SFL017 - Tooling must be able to provide a dependency tree of a feature or
application model.
-* SFL020 - Tooling must support runtime launching of an application.
-* SFL030 - Tooling must be able to introspect and potentially override the
startup order of bundles for an application.
-* SFL035 - Tooling should support overriding certain values, for example a
bundle version, in an application model at launch time.
-* SFL040 - Tooling must support substitution of variable values at launch time.
-* SFL045 - If a variable name is not specified the and does not have a default
in the feature model, the launching process must not proceed.
-* SFL050 - When an application is started, the install and the startup order
of bundles should be the same, ensuring that the bundles are shutdown in
reverse order and started in the same order on next startup of the framework.
-* SFL060 - Tooling must support multiple versions of a feature and only select
the highest version of a feature to launch the application.
-* SFL070 - Tooling must be able to differentiate between a feature and an
update of a feature. An update should only be included in the application of
the base feature is included.
-
-## Container Requirements
-
-These requirements are not directly related to the feature model itself, but
rather running a feature based OSGi application within a container.
-
-* SFC010 - The feature model must support operation in a container environment
such as Docker.
-* SFC020 - The feature model must support micro-services oriented target
runtimes where a single micro service runs in its own container containing only
the binaries required for that microservice.
-* SFC030 - It must be possible to add new features by placing additional files
in a container's file system.
-* SFC040 - It must be possible to alter existing features by placing
additional files in the file system. For example to uninstall or update a
bundle provided by an existing feature or to alter a configuration set by an
existing feature.
-* SFC050 - The feature model must enable the creation of container (Docker)
images for a specified set of features.
-
-## Sling Specific Requirements
-
-These requirements are important for Apache Sling in order to have a full
replacement for the current provisioning model. Ideally, these requirements are
already covered by the general requirements.
-
-* SFS010 - The feature model must support JCR Repository Initialization via
the _repoinit_ language. See SFM240
-* SFS020 - The feature model must support features which contains repository
content packages. See SFM200
-* SFS030 - The feature model should support all functionality previously
provided by the Sling provisioning model.
-* SFS040 - A (Maven) tool must be provided that can create a launchable Sling
Starter application from the feature model.
--
To stop receiving notification emails like this one, please contact
[email protected].
