[jira] [Resolved] (SLING-10056) Make feature self contained with respect to origins for configurations and properties

["Carsten Ziegeler (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-10056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-10056.
--------------------------------------
    Resolution: Fixed

Implemented in by introducing a cache (feature id -> region). The cache is optional and if not available , the feature provider must be able to provide the feature (as before)

https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/commit/ac96ecce9109d487a803b9119ecb6a032830629e

> 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
>            Priority: Major
>             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)