Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337668 - C/C++ general settings do not persist across restarts of Eclipse
Summary: C/C++ general settings do not persist across restarts of Eclipse
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 7.0.1   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-20 13:46 EST by yk.bugzilla CLA
Modified: 2020-09-04 15:27 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description yk.bugzilla CLA 2011-02-20 13:46:40 EST
Build Identifier: 20100917-0705

Under Window->Preferences->C/C++->General Settings for C/C++ Development, the options for "Build Scope" (Build active configuration versus build all configurations) and "Build configurations only when there are Eclipse resource changes within the project and its references" do not persist across restarts of Eclipse. the options do apply during the current instance of Eclipse, but once Eclipse is restarted, the options revert to default. This bug occurs in both Ubuntu 10.04 and Windows 7; in previous versions it occurs on Mac OS X, but I haven't had access to a mac to test more recently. I haven't tested other operating systems.

Reproducible: Always

Steps to Reproduce:
1. Go to Window->Preferences->C/C++->General Settings for C/C++ Development and select "Build all configurations in each project" and check mark "Build configurations only when there are Eclipse resource changes within the project and its references".
2. Restart Eclipse.
3. Go to Window->Preferences->C/C++->General Settings for C/C++ Development. The options have reverted to default (Build active configuration and unchecked).
Comment 1 Marc-André Laperle CLA 2011-02-21 14:51:06 EST
I can reproduce with 7.0.0 but not 8.0. Looks like this has been fixed with bug 334118.