There are two major points, any dependencies
from the product to the optional features should be expressed using version
ranges. This is what Brian's suggestion with the p2.inf does.
The second part is the extra director
calls to add the features as top level installed items so that the regular
update considers them.
In PDE/Build there are customization
points that allow performing this director call before the archive is created,
I don't know if there is anything similar in Tycho.
Brian de Alwis <briandealwis@xxxxxxxxx>
P2 developer discussions
05/17/2012 07:32 AM
it possible to install a feature into an RCP app at
On Wednesday, 16 May 2012, Trace Windham wrote:
Unfortunately, it is not installed at the root level of
installed features. Instead, the feature is a child of the main RCP
feature of my RCP application, and therefore when updates are available
for this child feature they are not found during the execution of the "Check
For Updates" command in my RCP application. My requirement is
that this feature be independently updatable without having to be manually
installed by a user. I think this is what the patch in bug 361722
Do you think I'm accurate in this explanation? I'm not
yet confident of my knowledge in this area.
Technically these features can still be updated by p2
independently of the product, even though they aren't root-level. But
I guess the p2 Update UI only considers root-level IUs.
So I guess your antrun to install via the director is
the best approach for now.