[KARAF-5376] Processor mechanism for feature definitions (a.k.a. "better overrides")

• Type: Proposal
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.2.0.M2
• Component/s: karaf
• External issue URL: http://mail-archives.apache.org/mod_mbox/karaf-dev/201709.mbox/%3CCAAdXmhoXjtqHi5N7WJPX_1xkSsJrNAOGYn-PVprDAJZM76u5eg%40mail.gmail.com%3E
• Assignee: Grzegorz Grzybek
• Reporter: Grzegorz Grzybek
• Created: 14/Sep/17 10:08
• Updated: 26/Oct/18 09:58
• Resolved: 11/Dec/17 16:52

Description

It'd be good to have a mechanism that could transform/enhance/process feature definitions after reading them from original feature XML descriptors and before passing them to Karaf features deployer.

Current overrides mechanism could be generalized beyond simple version change for <feature>/<bundle> URIs.

Issue Links

• is related to: KARAF-4181 blacklist.properties and overrides.properties are not properties file
• is related to: KARAF-5372 startup.properties doesn't respect overrides
• is related to: KARAF-5591 Blacklisted features should be considered as dependencies and/or conditionals
• is related to: KARAF-4329 Consider bundles from override.properties while creating the assembly
• is related to: KARAF-5273 karaf-maven-plugin assembly should take feature wildcards
• is related to: KARAF-5339 Allow to define blacklisted bundles in a profile
• is related to: KARAF-5540 Document new "features processor"
• relates to: KARAF-5990 Blacklisted dependent features should be skipped during assembly generation
• relates to: KARAF-3635 Provide a black list for features
• links to: GitHub Pull Request #434