commit | 40b24975d6604dcec9d1711ef2771ea34ad95c2f | [log] [tgz] |
---|---|---|
author | David Bosschaert <bosschae@adobe.com> | Tue Nov 06 13:58:43 2018 +0000 |
committer | David Bosschaert <bosschae@adobe.com> | Tue Nov 06 13:58:43 2018 +0000 |
tree | abc446bcc4e47a3655afd48642bb10403edcccf7 | |
parent | bbea2ae426a7b132f9d56e685e0c6580b8276ec4 [diff] |
Handle extension merging with null target
This component contains extensions relating to the API Regions component. The following extensions are registered via the ServiceLoader mechanism:
org.apache.sling.feature.builder.MergeHandler
Merge handlers are called when features are merged during the aggregation process.
APIRegionMergeHandler
- This handler knows how to merge API Regions extensions and adds the org-feature
key to the api-regions
sections to record what feature this section originally belonged.
org.apache.sling.feature.builder.PostProcessHandler
PostProcessHandlers are called when a feature contains an api-regions
section.
BundleMappingHandler
- This handler creates a mapping file idbsnver.properties
that maps the Artifact ID to a bundle symbolic name and version. A tilde ~
is used in the value of the map to separate BSN and version.
BundleArtifactFeatureHandler
- This handler creates 3 mapping files:
bundles.properties
: maps bundles to the original feature they were in. A bundle could be from more then one feature.features.properties
: maps features to regions. A feature can be in more than one region.regions.properties
: maps regions to packages. A region can expose more than one package.The location of the files created by the BundleArtifactFeatureHandler
handler is stored in a system property with name apiregions.
+ filename. So to obtain the file name of the bundles.properties
file, make the following call:
System.getProperty("apiregions.bundles.properties")