Hi Paul,
So thanks to you and the link, I've been able to fix my problem. I had to remove the ccw feature definition from the product features list, and instead add a
requires.x.name to my product's ccw.p2.inf file.
And the final step is to manually invoke the Director to install ccw.feature.feature.group to the product after the fact.
This is why I'm coming back to you. Since I've removed ccw.feature from the product features list, I don't find feature artifacts in my product's target/repository repository anymore. Before that, it was easy to point the Director to this directory.
So Ive pointed instead the directory to a relative path like ../ccw.updatesite/target/repository.
And it is working for ccw.feature, great !
BUT
I'd also like to make other features updatable independently by the user: egit, eclipse-colorthemes for instance.
And then starts the redundancy : I have already declared where to find these feature in my ccw.target.e47 target definition, but I don't know how to reuse this.
Instead, I find myself repeating tycho-eclipserun-plugin calls, an for each call, pasting the location of external p2 repositories ...
There must be a better way with tycho, right ? I'm sure I'm not using it to its full potential ....
thanks in advance for any guidance,
--
Laurent