Bug 229328 - org.eclipse.cdt.make.core.buildLocation in .project seems not to be refreshed when changing the current configuration
Summary: org.eclipse.cdt.make.core.buildLocation in .project seems not to be refreshed...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 4.0.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-29 10:24 EDT by Philipp Bachmann CLA
Modified: 2020-09-04 15:20 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Bachmann CLA 2008-04-29 10:24:29 EDT
Build ID: M20080221-1800

Steps To Reproduce:
1. Store a C++ Managed Make project with active configuration "Release" in CVS (to later compare the .project file to, not because this issue was CVS related).
2. Change the active configuration via the "Manage configurations for the current project" button in the toolbar of the C++ perspective from "Release" to "Debug".
3. Compare via "Team/Synchronize with Repository" the .project file with the former version: You won't see any differences. This does not conform to my expectation - I'd like to see "org.eclipse.cdt.make.core.buildLocation" changed.
4. Open project properties, click "Manage configurations" within "C/C++ Build" category. You will see the "Debug" configuration flagged "Active" - which is what I expected.
5. Don't change anything and confirm both the "Manage Configurations" and the "Properties" dialog with "Ok".
6. Again compare via "Team/Synchronize with Repository" the .project file with the former version: Now you will see a difference.


More information:
Even though the two ways to change the active configuration seem equivalent, with respect to the .project file currently they are not.

I report this because I intend to avoid unnecessary changes to files like .project on checkin. So if I accidentally changed the active configuration via the "Manage Configurations" dialog and so got my .project file changed I cannot simply get rid of the change by using the via the "Manage configurations for the current project" button in the toolbar of the C++ perspective, because this does not propagate the change back to the .project file.