[jira] [Resolved] (SLING-7977) When merging features artifacts should keep an association with their originating feature

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

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

David Bosschaert resolved SLING-7977.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: Feature Model 0.1.4

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

> When merging features artifacts should keep an association with their originating feature
> -----------------------------------------------------------------------------------------
>
>                 Key: SLING-7977
>                 URL: https://issues.apache.org/jira/browse/SLING-7977
>             Project: Sling
>          Issue Type: New Feature
>          Components: Feature Model
>    Affects Versions: Feature Model 0.1.2
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>            Priority: Major
>             Fix For: Feature Model 0.1.4
>
>
> When features are merged, artifacts such as bundles are merged into a single feature. For certain operations, for example API whitelisting it must be possible to know what the original feature was that contained the artifact.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)