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 2020/02/13 08:48:00 UTC

[jira] [Closed] (SLING-9024) API Regions runtime should prefer named regions from the Global region

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

Carsten Ziegeler closed SLING-9024.
-----------------------------------

> API Regions runtime should prefer named regions from the Global region
> ----------------------------------------------------------------------
>
>                 Key: SLING-9024
>                 URL: https://issues.apache.org/jira/browse/SLING-9024
>             Project: Sling
>          Issue Type: Task
>          Components: Feature Model
>    Affects Versions: Feature Model API Regions Runtime Fragment 1.0.6
>            Reporter: A. J. David Bosschaert
>            Assignee: A. J. David Bosschaert
>            Priority: Major
>             Fix For: Feature Model API Regions Runtime Fragment 1.0.8
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> If a package resolution candidate for a package requirement is available from the {{global}} region and another named region which overlaps with the regions that the requiring bundle is in, then the {{global}} region candidate should be discarded.
> Let's say a bundle in the {{foo}} region requires a package which is provided by two bundles. One of the bundles is in the {{foo}} region and another bundle is in the {{global}} region. Then the candidate from the {{global}} region must be discarded so that the requiring bundle only wires to candidates from its own region.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)