[
https://issues.apache.org/jira/browse/SLING-12464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17894000#comment-17894000
]
Carsten Ziegeler commented on SLING-12464:
------------------------------------------
I agree that we could try to limit this. We (=AEM) have a use case for four
regions, global, deprecated, internal and customer - which would result in two
possible graphs:
{noformat}
global
/ \
deprecated customer
|
internal
{noformat}
or
{noformat}
global
|
deprecated
/ \
internal customer
{noformat}
> Allow disjunct API regions
> --------------------------
>
> Key: SLING-12464
> URL: https://issues.apache.org/jira/browse/SLING-12464
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Affects Versions: Feature Model API Regions Extension 2.0.0
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently API regions always form a line, i.e. one is always a superset of
> the other. The documentation at
> https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/docs/api-regions.md#visibility-of-java-api
> explicitly states:
> bq. Exports declared earlier in the api-regions array also apply to later
> elements in the array
> That currently prevents having completely disjunct API regions (not sharing
> any exported-packages).
> A use case for disjunct API regions was discussed in
> https://lists.apache.org/thread/mh36p586vqhxsvkjz6lsgmtf1cz3d99g.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
