Description
This would be very beneficial when trying to provide some kind of "patched" distributions of Karaf and based applications.
When installing features, if you want to modify a bundle, the only way is to release a new feature file which can be problematic, especially when the target bundle is a transitive dependency, because you then need to release multiple features descriptors in various projects.
The idea is to provide a simple file in etc/overrides.properties which will contain a list of bundle urls to consider as replacements when installing features. Before installation, bundles will be scanned for matching overrides.
Matching is done so that the target and override bundles must have the same symbolic name and the target bundle version must has the same major and minor version than the override bundle. This version range can be specified manually using something like:
url;range="[2,3)"
in which case, any target bundle matching the version range and the symbolic name will be overriden.
Attachments
Issue Links
- relates to
-
KARAF-4180 Document overrides configuration
- Resolved