[SLING-10575] Bundles without feature-origin result in empty bundle to feature mapping

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Installer Factory Feature Model 0.5.0
• Fix Version/s: Installer Factory Feature Model 0.6.0, Feature Model API Regions Extension 1.3.6
• Component/s: Feature Model
• Assignee: Carsten Ziegeler
• Reporter: Dirk Rudolph
• Created: 30/Jun/21 15:01
• Updated: 06/Jul/21 07:06
• Resolved: 01/Jul/21 09:43

Description

When installing a feature archive of a feature similar to the following

{
  "id":"com.exmaple:my-feature-pkg:slingosgifeature:tiera:12345-SNAPSHOT",
  "bundles":[
    {
      "id":"com.example:my-bundle:1.2.3-SNAPSHOT",
      "start-order":"20"
    }
  ],
  "api-regions:JSON|false":[
    {
      "name":"global",
      "exports":[
        "com.example.my"
      ]
    }
  ]
} 

A bundle to feature mapping like

com.example:my-bundle:1.2.3-SNAPSHOT=

will be created in the feature's org.apache.sling.feature.apiregions.factory configuration. This is because the bundle does not specify any feature-origin(s).

For those cases the feature it self should be the origin of the bundle. The current version of the api regions runtime will otherwise not find the feature a bundle belongs to and so may not be able to resolve the api regions the bundle belongs to.

An example where that can happen is the usage of the slingfeature-maven-plugin without using the aggregation feature. When just building far from a hand-crafted feature model the feature-origin may not be set on the api-region(s).

Issue Links

• links to: GitHub Pull Request #2