hi,
I'm facing the situation that I'd like to ship a new version of a
feature via an update site and the new feature doesn't contain a plugin
the previous version of the feature did contain. After installing the
new feature, I'd expect eclipse not to load the "orphaned" plugin.
However, this doesn't seem to be the case... which is troublesome in my
case since this "orpahned" plugin has dependencies on the old versions
of the other plugins which practically ensures that p2 activates all new
*and* old versions of the plugins.
Example: Think of
example.feature-v1
|-example.core-v1
|-example.ui-v1
\-example.experimental-v1
with example.experimental-v1 depending on example.ui-v1 and
example.core-v1.
Now, I'd like to ship:
example.feature-v2
|-example.core-v2
\-example.ui-v2
Note that now example.experimental is not included anymore. After
updating the feature from v1 to v2, it seems that P2 therefore sticks
with example.experimental-v1, since there is no update for it. Due to
the dependencies this forces P2 to activate example.ui-v1 and
example.core-v1 as well.
So how can I assure that plugins, which are not included in a new
version of a feature, are deactivated or removed?
thanks for your advice,
Moritz