[
https://issues.apache.org/jira/browse/SLING-7829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617406#comment-16617406
]
ASF GitHub Bot commented on SLING-7829:
---------------------------------------
karlpauls opened a new pull request #3: SLING-7829: Change the includes to be
include and from a list to a si…
URL: https://github.com/apache/sling-org-apache-sling-feature-io/pull/3
…ngle (optional) field
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Reduce feature include to allow only one feature
> ------------------------------------------------
>
> Key: SLING-7829
> URL: https://issues.apache.org/jira/browse/SLING-7829
> Project: Sling
> Issue Type: Task
> Components: Feature Model
> Reporter: Carsten Ziegeler
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Feature Model 0.1.4, Feature Model IO 0.1.4
>
>
> Currently a feature can include a list of features (modify them by removal)
> and aggregate this.
> However, the include mechanism has never been intended to act as an
> aggregation mechanism. Its rather intended to adjust an existing feature,
> basically creating an own variant of a feature.
> Therefore we should limit the include mechanism to a single feature.
> We might probably also rename this to something better
> We might also add a flag like "final" to a feature, which indicates that this
> feature can't be "included/modified" by another feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
