Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368755

Summary: [remotecdt] Remote C/C++ Launch created with CDT 7.0 is not migrated to CDT 8.0
Product: [Tools] CDT Reporter: Martin Oberhuber <mober.at+eclipse>
Component: cdt-debugAssignee: Anna Dushistova <anna.dushistova>
Status: CLOSED WONTFIX QA Contact: Ken Ryall <ken.ryall>
Severity: normal    
Priority: P3 CC: anna.dushistova, cdtdoug, marc.khouzam, pawel.1.piech, uwe.st
Version: 8.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Martin Oberhuber CLA 2012-01-16 13:01:46 EST
Build ID: CDT 8.0 (Indigo)

Remote C/C++ Launches created in a workspace with CDT 7.0 are not migrated to CDT 8.0 format when upgrading Eclipse, but retaining the Workspace.

This breaks the typically expected contract of Workspace compatibility, and is not mentioned in the New & Noteworthy. Customers complain that their pre-existing launches don't work any more.

Steps to Reproduce:
1. Launch CDT 7.0, create a new REmote C/C++ Application Launch 
2. Open the same workspace with CDT 8.0 -- the Launch is not visible any more.

I think the problem is simply that the old launch configuration type was
    "org.eclipse.rse.remotecdt.RemoteApplicationLaunch"
whereas the new type is now
    "org.eclipse.cdt.launch.remoteApplicationLaunchType"
migration code should be added which copies the old Launches into the new ones the first time an old workspace is opened with CDT 8.0.x
Comment 1 Martin Oberhuber CLA 2012-01-16 13:14:23 EST
CQ:WIND00328654

Getting this fixed in CDT 8.0.2 would be great, such that workspace compatibility remains intact.
Comment 2 Anna Dushistova CLA 2012-02-10 10:46:48 EST
Martin,
Do you know if a migration delegate can be contributed separately like a launch delegate?
The launch configuration type definition now lives in org.eclipse.cdt.debug.code and I am not quite sure we can implement migrate(...) without introducing a dependency on org.eclipse.cdt.launch.remote.
Comment 3 Uwe Stieber CLA 2012-09-13 04:16:44 EDT
Anna,
AFAIK, there is no extension point to contribute a migration delegate separately. And if I'm not mistaken, even if a migration delegate is specified for a launch configuration type, the migration does not happen automatically. The user has to got the "Launch Configurations" preferences page to trigger the migration.
Comment 4 Marc Khouzam CLA 2015-05-25 11:29:24 EDT
Is this old enough that it is not a problem any more? I'm not sure we need to worry about CDT 7.0.

Marking as WONTFIX.

Feel free to re-open if you disagree.