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

radu 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 57479c5  typo
57479c5 is described below

commit 57479c563c0b57dd6bc6626c3d5ea12b2a70d4ba
Author: Radu Cotescu <r...@cotescu.com>
AuthorDate: Tue Mar 13 09:16:17 2018 +0100

    typo
---
 featuremodel/requirements.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/featuremodel/requirements.md b/featuremodel/requirements.md
index b5d61bf..b575039 100644
--- a/featuremodel/requirements.md
+++ b/featuremodel/requirements.md
@@ -44,7 +44,7 @@ The feature model is about describing a feature, aggregating 
features to either
 * 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 
now way of explicitly requiring a feature from another feature.
+* 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.

-- 
To stop receiving notification emails like this one, please contact
r...@apache.org.

Reply via email to