[SLING-10858] Incorrect API Regions generated in features

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Content-Package to Feature Model Converter 1.1.6
• Fix Version/s: Content-Package to Feature Model Converter 1.1.12
• Component/s: Content-Package to Feature Model Converter
• Assignee: Karl Pauls
• Reporter: A. J. David Bosschaert
• Created: 07/Oct/21 15:52
• Updated: 14/Mar/22 22:49
• Resolved: 15/Nov/21 10:34

Description

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 no 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 being processed, and as such the api-regions exports are bleeding between generated features.

Issue Links

• links to: GitHub Pull Request #116