Community
Participate
Working Groups
Created attachment 258217 [details] Two same launches in the launch configuration dialog after project copy Overview: The problem to create launch configuration for project, which would be actual after project-copy-paste or project-rename action. After these actions user need's to improve launch configuration to make it available and working. Even if launch configuration exits in project's folder. Steps to Reproduce: 1. Create a new C-Project cross1: File->New->C Project->Executable->Hello World->Cross GCC 2. Create new launch configuration, save it in project directory and use variables for application for run/debug: Main->C/C++ Application: ${project_loc}/Debug/${project_name}.exe Here it's good to consider, that launch configuration could be also created from the project-template during project creation, without any user action. 3. Go to the launch file, see that project name is stored there (cross1) <stringAttribute key="org.eclipse.cdt.launch.PROGRAM_NAME" value="${project_loc}/Debug/${project_name}.exe"/> <stringAttribute key="org.eclipse.cdt.launch.PROJECT_ATTR" value="cross1"/> <listEntry value="/cross1"/> 4. Copy project and paste it, give the name cross1_copy Actual Results: 1. Build the new project (cross1_copy) - new application cross1_copy.exe is created 2. In the the new project launch configuration file there is some content which is still related to original project instead of cross1_copy: <stringAttribute key="org.eclipse.cdt.launch.PROJECT_ATTR" value="cross1"/> <listEntry value="/cross1"/> 3. In the launch configuration dialog, there are 2 launch configurations, but each of them is related to original project (cross1_copy), see image in attachment. Expected Results: 1. There are should be no links to original project in the project_copy launch configuration file. 2. In the launch configuration dialog should be 2 launch configurations which would be related to different projects: one to original, second - to original copy.
The bug still exists in new CDT. Briefly, during copy process the new launch configuration actually created, but it is not named after the copy project and it is linked to original project. What we want: the launch configuration named after copy project and linked to copy project.