You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2018/11/20 17:36:00 UTC
[jira] [Created] (SLING-8123) Remove org-feature tracking from
feature model
David Bosschaert created SLING-8123:
---------------------------------------
Summary: Remove org-feature tracking from feature model
Key: SLING-8123
URL: https://issues.apache.org/jira/browse/SLING-8123
Project: Sling
Issue Type: Task
Components: Feature Model
Reporter: David Bosschaert
Fix For: Feature Model 0.8.0
Initially the org-feature attribute was added to artifacts in the feature model to facilitate API-Region handling in aggregated features: when features are aggregated they lose their origin and as such the API-Regions defined in the origins are all merged together.
However with the analyser now being called from the slingfeature-maven-plugin such dependencies can be checked statically before the aggregation is done via an analyser task, which means that the org-feature is not needed any more to record this information.
Therefore I would propose that the org-feature attribute is removed from artifacts and also from configurations where it is now also recorded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)