[
https://issues.apache.org/jira/browse/KARAF-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved KARAF-2752.
------------------------------------
Resolution: Fixed
https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=05521f5c365b8dfe081edfe39c0222228522009d
> Provide a way to override bundles at feature installation time
> --------------------------------------------------------------
>
> Key: KARAF-2752
> URL: https://issues.apache.org/jira/browse/KARAF-2752
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 3.1.0
>
>
> 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:
> {code}
> url;range="[2,3)"
> {code}
> in which case, any target bundle matching the version range and the symbolic
> name will be overriden.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
