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 2021/10/07 15:53:00 UTC
[jira] [Created] (SLING-10858) Incorrect API Regions generated in
features
A. J. David Bosschaert created SLING-10858:
----------------------------------------------
Summary: Incorrect API Regions generated in features
Key: SLING-10858
URL: https://issues.apache.org/jira/browse/SLING-10858
Project: Sling
Issue Type: Bug
Components: Content-Package to Feature Model Converter
Affects Versions: Content-Package to Feature Model Converter 1.1.10
Reporter: A. J. David Bosschaert
In some cases the cpconverter generates an {{api-regions}} section with {{global}} exports for packages, where the bundles providing those packages are not actually listed in the feature. I have seen features with _not_ bundles (just some configuration) and an {{api-regions}} section with lots of exports, which clearly couldn't be satisfied by the feature as it did not have any bundles at all.
I believe that this might be caused by the fact that the DefaultFeaturesManager has the an apiRegionsExports field
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/blob/master/src/main/java/org/apache/sling/feature/cpconverter/features/DefaultFeaturesManager.java#L101
which is not cleared between features, and as such the api-regions exports are bleeding between generated features.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)