Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Updating a feature after renaming id

I'm afraid changing the id of an existing feature/bundle is a bad idea.
If I understand correctly, what you want to achieve is to make sure the feature with the old id gets uninstalled when the new feature is installed/updated, am I right ?
There is a P2 touchpoint action that allows to uninstall some feature but I never figure out how to use it as it seems you need to know the full feature coordinates (including the version) and I don't know the behaviour if the feature you want to uninstall is not present but I'm afraid it will raise an error


On Tue, Jan 8, 2013 at 7:38 PM, Julien HENRY <henryju@xxxxxxxx> wrote:

This is not a tycho specific question but instead a p2/eclipse question but I don't where to ask. Please redirect me if you think this is not appropriate.

In our Eclipse plugin we have a feature that has been replaced by another one with a different id. In order to ease migration for end users I have added the following instructions in the p2.inf of the new feature: =
update.range = [0.0.0,3.0.0)
update.severity = 0
update.description = Update feature with old ID.

It works fine as long as user try to update from old.feature to new feature. But in case user has already updated to new feature (in our case a release candidate of the 3.0.0 version) then they are no more allowed to update as it seems new feature is not considered as a valid update for previous new feature

I tried to add 2 possible updates in the p2.inf: =
update.0.range = [0.0.0,3.0.0)
update.0.severity = 0
update.0.description = Update feature with old ID. =
update.1.range = [0.0.0,$version$)
update.1.severity = 0
update.1.description = Update feature with new id.

But it doesn't work as in the resulting content.xml there is only one <update> element under the <unit id="">.

Do you know if it is a valid expectation to have several <update> elements under <unit>? In this case what is the way to achieve this?



tycho-user mailing list


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

Back to the top