This is an automated email from the ASF dual-hosted git repository.

cziegeler 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 ce14d48  Update references to general requirements
ce14d48 is described below

commit ce14d483c8f6daa5778ed1db467997249b4e2c57
Author: Carsten Ziegeler <cziege...@apache.org>
AuthorDate: Mon Feb 19 17:32:48 2018 +0100

    Update references to general requirements
---
 featuremodel/readme.md | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/featuremodel/readme.md b/featuremodel/readme.md
index 40fc31b..b1e8b27 100644
--- a/featuremodel/readme.md
+++ b/featuremodel/readme.md
@@ -58,17 +58,17 @@ The following requirements relate to tooling around the 
Feature Model.
 * SFT010 - Tooling must support runtime launching with one or more features.
 * SFT020 - 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.
 * SFT030 - Tooling must be able to compute the capabilities of a feature by 
inspecting the feature's content and directly specified capabilities.
-* SFT040 - Given one or more root features, the feature model must be able to 
compute the start order of all resulting features so that dependencies of 
features are started first. 
+* SFT040 - Given one or more root features, the feature model must be able to 
compute the start order of all resulting features so that dependencies of 
features are started first.
   * Comment(CZ) : Is this tooling or feature model?
   * Comment(DB) : It could be either, but if there is support for explicit 
ordering of features (SFM350) then a tool could compute the ordering beforehand 
and place it in this file.
 * SFT050 - Tooling must be able to find all features that provide the 
capabilities required by a given feature, from a set of available features.
 * SFT060 - It should be possible to dynamically install and uninstall features 
at runtime.
-* SFT070 - The feature model must support variable substitution for its values 
at runtime. 
+* SFT070 - The feature model must support variable substitution for its values 
at runtime.
   * Comment(CZ) : What exactly does this mean? Substitution of what?
-  * Comment(DB) : Like configuration values or bundle versions. Meaning that 
you can write something like ${db.user} instead of having to hardcode the user 
in the feature file. 
-* SFT080 - The feature model should allow the arbitrary text files to be 
written to the file system, to support configuration of components that use 
file-based configuration such as properties or XML files, such as web.xml. 
+  * Comment(DB) : Like configuration values or bundle versions. Meaning that 
you can write something like ${db.user} instead of having to hardcode the user 
in the feature file.
+* SFT080 - The feature model should allow the arbitrary text files to be 
written to the file system, to support configuration of components that use 
file-based configuration such as properties or XML files, such as web.xml.
   * Comment(CZ) : Not sure what this actually means, how does web.xml play a 
role here?
-  * Comment(DB) : Basically to configure entities that are not configured via 
OSGi configadmin. Web.xml is just an example. They might need a text file such 
as an xml file or some other file to exist in a given location to function. The 
idea would be that the feature model could write out this file. So it would not 
be a tooling requirement but rather a feature model runtime requirement. 
+  * Comment(DB) : Basically to configure entities that are not configured via 
OSGi configadmin. Web.xml is just an example. They might need a text file such 
as an xml file or some other file to exist in a given location to function. The 
idea would be that the feature model could write out this file. So it would not 
be a tooling requirement but rather a feature model runtime requirement.
 
 ### Containers
 These requirements
@@ -81,9 +81,8 @@ These requirements
 
 ### Sling Specific
 
-* SFS010 - The feature model must support JCR Repository Initialization via 
the _repoinit_ language.
-  * Comment(DB) : I guess the SFM0190 reference that was in this req is not 
valid any more? I don't see the relation to SFM190? Same for next requirement. 
-* SFS020 - The feature model must support features which contains repository 
content packages.
+* 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
cziege...@apache.org.

Reply via email to