Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migration paths needed

2014-01-10 Thread Andreas Sewe
Hi, > This problem looks like it's not caused by the migration of your > sub-features and you'll probably get a different result with e.g. an Eclipse > Classic with Code Recommenders 1.x installed and attempting the update there. > > Rather, it's not possible to replace the old o.e.r.rcp.feature

Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migration paths needed

2014-01-10 Thread Carsten Reckord
Hi, This problem looks like it's not caused by the migration of your sub-features and you'll probably get a different result with e.g. an Eclipse Classic with Code Recommenders 1.x installed and attempting the update there. Rather, it's not possible to replace the old o.e.r.rcp.feature with somet

Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migration paths needed

2014-01-10 Thread Andreas Sewe
Hi again, >> 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

Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migration paths needed

2014-01-10 Thread Andreas Sewe
On 10.01.14 15:03, David M Williams wrote: > I barely read your original note ... I stopped when I got to the part > about "Major version change" in "Maintenance stream". That sounds like > "API change" or some other incompatible change ... which would not be > appropriate in "SR2 maintenance". I'm

Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migration paths needed

2014-01-10 Thread David M Williams
I barely read your original note ... I stopped when I got to the part about "Major version change" in "Maintenance stream". That sounds like "API change" or some other incompatible change ... which would not be appropriate in "SR2 maintenance". I'm sure I could be missing your point ... but ...

Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migration paths needed

2014-01-10 Thread Andreas Sewe
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 > sc

Re: [cross-project-issues-dev] Kepler SR2: Advice on feature-rename migration paths needed

2014-01-10 Thread Igor Fedorenko
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. -- Regards

[cross-project-issues-dev] Kepler SR2: Advice on feature-rename migration paths needed

2014-01-10 Thread Andreas Sewe
Hi, the Code Recommenders project contributes both to the Kepler and Luna simultaneous releases. So far, we have contributed version 1.x to Kepler (R and SR1) and 2.x to Luna (M1-M4). Given that version 2.x has proven to be stable (we are at 2.0.4 at the moment) we would like to contribute Code Re