|How is installFeature action supposed to work? [message #899135]
||Mon, 30 July 2012 11:53
| Thorsten Meinl
Registered: July 2009
We are currently facing the problem of turning an implicitly installed
feature (from a feature dependency) into a root feature via an update to
the RCP application. I though that could be accomplished with the
installFeature touchpoint action, but this does not work, because the
feature to be installed by this action must be among the artifacts of
the current feature. This is obviously not the case, I have never seen
an feature.group being the artifact of another feature (is this even
possible?). This is a bit disappointing since this seemed to be the only
way of accomplishing the task. Two question:
1. Why is installFeature restricted to artifacts of the current IU
(which in almost all cases does not make sense I believe)?
2. Is there another way of turning a non-root IU into a root IU without
explicitly installing the IU?
The overall goal is to make the non-root IU uninstallable, which isn't
possible if it isn't a root IU (only).