Hi Konrad, The API Regions are not declared by bundles but only expressed in the api-regions extension in the feature model. So I'm not sure how the API Jar could contain the API Regions as they are not associated with the Bundle.
I think the API Regions the way we currently have them can only be part of a feature model. We _could_ represent them a OSGi Capabilities in the feature model, but that would basically just duplicate the information that's already in the api-regions section, so I'm not sure how much value that would add. My 2c, David On Fri, 13 Nov 2020 at 11:55, Konrad Windszus <[email protected]> wrote: > Hi everyone, > I would like to gather some feedback on > https://issues.apache.org/jira/browse/SLING-9883 < > https://issues.apache.org/jira/browse/SLING-9883>. > I already provided a draft PR (lacking tests for now) in > https://github.com/apache/sling-slingfeature-maven-plugin/pull/59 < > https://github.com/apache/sling-slingfeature-maven-plugin/pull/59>. > > IMHO using the bnd-resolver-maven-plugin helps to detect a lot of runtime > issues already at compile time. I introduced that in > https://github.com/apache/jackrabbit-filevault < > https://github.com/apache/jackrabbit-filevault> some time ago and it > turned out to be very useful. > > The only thing I am not sure about is API Regions, as you cannot tell from > an OSGi-Capability to which package it belongs. Any idea how one could > support that? > > Thanks, > Konrad > >
