[jira] [Resolved] (SLING-8123) Remove org-feature tracking from feature model

["David Bosschaert (JIRA)" <ji...@apache.org>]

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

David Bosschaert resolved SLING-8123.
-------------------------------------
    Resolution: Fixed

Fixed in https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-feature.git;a=commitdiff;h=28c743415ea1d236b3a22425370b1002554b26c6

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