You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "A. J. David Bosschaert (Jira)" <ji...@apache.org> on 2020/10/14 17:15:00 UTC
[jira] [Updated] (SLING-9827) Specify the API Region to export
packages into
[ https://issues.apache.org/jira/browse/SLING-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
A. J. David Bosschaert updated SLING-9827:
------------------------------------------
Description:
Make it possible to specify that all packages exported by bundles in a content package will be exported in a given region.
By default the packages are not listed, which is ok if the generated feature doesn't opt in to the API Regions mechanism. In that case the packages are implicitly visible in the {{global}} region.
However, if the generated feature does opt into the API Regions (for example by specifying the {{-r}} / {{--api-region}} option), then it will be necessary to also explicitly list the exported packages in the API Regions exports, as otherwise they will not be visible across the features if multiple features are generated from a single content package (e.g. to handle run modes).
was:
Make it possible to specify that all packages exported by bundles in a content package should be exported in a given region.
By default the packages are not listed, which is ok if the generated feature doesn't opt in to the API Regions mechism. In that case the packages are implicitly visible in the {{global}} region.
However, if the generated feature does opt into the API Regions, then it will be necessary to also explicitly list the exported packages in the API Regions exports, as otherwise they will not be visible across the features if multiple features are generated from a single content package (e.g. to handle run modes).
> Specify the API Region to export packages into
> ----------------------------------------------
>
> Key: SLING-9827
> URL: https://issues.apache.org/jira/browse/SLING-9827
> Project: Sling
> Issue Type: Improvement
> Components: Content-Package to Feature Model Converter
> Affects Versions: Content-Package to Feature Model Converter 1.0.14
> Reporter: A. J. David Bosschaert
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.0.16
>
>
> Make it possible to specify that all packages exported by bundles in a content package will be exported in a given region.
> By default the packages are not listed, which is ok if the generated feature doesn't opt in to the API Regions mechanism. In that case the packages are implicitly visible in the {{global}} region.
> However, if the generated feature does opt into the API Regions (for example by specifying the {{-r}} / {{--api-region}} option), then it will be necessary to also explicitly list the exported packages in the API Regions exports, as otherwise they will not be visible across the features if multiple features are generated from a single content package (e.g. to handle run modes).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)