You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2021/01/11 10:49:00 UTC
[jira] [Created] (SLING-10056) Make feature self contained with
respect to origins for configurations and properties
Carsten Ziegeler created SLING-10056:
----------------------------------------
Summary: Make feature self contained with respect to origins for configurations and properties
Key: SLING-10056
URL: https://issues.apache.org/jira/browse/SLING-10056
Project: Sling
Issue Type: Improvement
Components: Feature Model
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Feature Model API Regions Extension 1.1.18
When features are aggregated, configurations and framework properties get metadata with their feature origins.
When now a configuration api is used on an aggregated feature, it is currently required that the feature origins (which might be different features) are all available (via a feature provider). This makes the feature not self-contained in such a scenario anymore which should be avoided to easier pass around such a feature.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)