Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340209 - Project-specific configuration-relations setting is never persisted anywhere
Summary: Project-specific configuration-relations setting is never persisted anywhere
Status: RESOLVED DUPLICATE of bug 205299
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 8.0   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Doug Schaefer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-16 14:20 EDT by Baltasar Belyavsky CLA
Modified: 2011-03-16 14:49 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Baltasar Belyavsky CLA 2011-03-16 14:20:35 EDT
It is impossible to change the configuration-relations setting on the project-scope because it doesn't get persisted anywhere. The setting is only saved in memory, so it does stick until you close/reopen the project, or delete/reimport it.

Steps to reproduce:

1. Create a simple C project.
2. Go to project Properties > C/C++ General > Indexer page.
3. Set the "Enable project specific settings" and the "Store settings with project" checkboxes.
4. Change the "Build configuration for indexer" setting to "Use active build configuration". Click OK.
-> Reopen the dialog - the setting does stick.
5. Close and reopen the project and check the same setting again.
-> The setting is reset back to the default "Use a fixed build configuration".

This setting is meant to be persisted into the .cproject file. If I manually add it into the .cproject (see "configRelations=2" below), then it does stick:
---
<cproject storage_type_id="org.eclipse.cdt.core.XmlProjectDescriptionStorage">
   <storageModule configRelations="2" moduleId="org.eclipse.cdt.core.settings">
   ...
---
Comment 1 Andrew Gvozdev CLA 2011-03-16 14:49:29 EDT
marking as duplicate:

*** This bug has been marked as a duplicate of bug 205299 ***