Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migr

[Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>]

Hi Igor,

> Do you need to do any "real" migration from 1.x to 2.x, for example
> workspace data format upgrades and the like, or it is purely feature
> rename? I vaguely remember there was way to tell p2 that one installable
> unit replaces another, which directly supports your feature rename
> scenario.

thanks for the pointer. I suppose you mean this [1]? The documentation
is a bit terse (and I am unsure whether Tycho fully supports p2.inf).
But I'll give it a try.

As for your question, Code Recommenders 1.x and 2.x store their data
differently, but they won't step on each others toes. And there really
is no need to migrate the data itself; it's mostly cached stuff which
will simply be downloaded anew in the 2.x format.

Best wishes,

Andreas

[1]
<http://wiki.eclipse.org/Equinox/p2/Customizing_Metadata#Update_descriptor_advice:>

-- 
Codetrails UG (haftungsbeschränkt)
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940