tried to deliver a custom provisioning action along with some other bundles and features via an update site. My intention is to do some custom stuff when the features contained in the site will be installed. Therefor I declared the bundle with my provisioning action as a meta requirement in each feature (via p2.inf).
Unfortunately, I always got 'java.lang.IllegalArgumentException: No action found for: ...'.
If the bundle with the provisioning action is already installed, p2 recognizes and invokes it...
So... is 'metaRequirements' broken or is it just not intended for my use case?
As far I can tell metaRequirements still work in Kepler.
Say that you are trying to install ABC and it has a meta requirements on ZZZ, where ABC would be the real feature you are trying to install and ZZZ is contributing some new p2 actions, then ZZZ and its dependencies must only use the touchpoint actions that are already installed.