H10 plugins left when upgrade to H11

[bdlink]

Using the 3.0.x update site, when I updated from H10 to H11, the H10 feature directories were replaces, but the H10 plugin directories are still there.

Also, the current H15 will not install because it is seen as earlier than H11 (since R2009...H11 > N2009...H15 ?).

[nickboldt]

Updates do not replace, they only add. If you want to replace, uninstall first, then install the updated version.

Uninstalling the older R H10 & H11 will also fix the issue that R > N even if the datestamp is newer, so you'll be able to install H15 (and beyond).

[bdlink]

You are saying that updates only add? This means that all of the old versions of modules will hang around? Sorry, I did not understand that, and it seems to me that the old modules hanging around would create a lot of trouble. Please clarify that this is what you mean.

My point is that an update should update, replacing what went before, not leaving it around. If the update to H10 is H11, should not the H10 plugin directories disappear?

[maxandersen]

There are two issues here:

Should H11 repelace H10 or update ?

1) Eclipse update manager works by *adding*, there is not mechanism for removing plugins. I've heard something about P2 will do some "garbage collecting" but I have not seen it in effect.

2) Why does the update not work at jboss tools nightly build update site ? We f*cked up and the R and N build got temporarily mixed up causing the problem you are having since you (un)luckily got the mixed up nightly build. Sorry for the trouble!

[bdlink]

No big trouble, these things happen when you are following nightly's.

I was mainly posting to raise what was happening. When eclipse claims there are no updates, usually installing the latest will update, this time not, so I investigated a bit more.

[nickboldt]

"bdlink" wrote:
You are saying that updates only add? This means that all of the old versions of modules will hang around? Sorry, I did not understand that, and it seems to me that the old modules hanging around would create a lot of trouble. Please clarify that this is what you mean.

My point is that an update should update, replacing what went before, not leaving it around. If the update to H10 is H11, should not the H10 plugin directories disappear?

I agree - and if you come from the Linux world then yes, update == replace with newer.

Eclipse, however, comes from the Windows world, where installing a new service pack or security fix means ADDING more code but not replacing it. So, yes, over time your Eclipse install will get bigger and bigger unless you do and uninstall to remove old version(s), then install something newer.

The only garbage collection that exists in the p2 installer AFAIK is that if you ask to remove plugin A which depends on plugin B, and nothing else needs B, it'll remove B too. But if you install A version 2.0.1 to update A version 2.0.0, you'll get both.

Stupid, I know, but there's nothing we can do about it. Hopefully the story has improved in Eclipse 3.5, due out in June.